I have hundreds of elements to enter manually to duplicate some forms in different databases since we cannot copy forms across databases.  I am trying to create and use some tools that could be called a Data Dictionary of Element Properties.

I already have Tom's utility, have made a number of modifications to it, but am still lacking a lot of information that I need.  So I have a few questions:

1.  I seem to recall seeing a list of codes for Element Types and Field Types.  But I cannot find/remember the list anywhere.  This must be the same source that Tom used in his tool.  Where are the master lists?  Do they change as new Sesame releases occur?  Are the existing lists current for 1.1.3?

2.  I need to get element properties for colors, fonts, sizes, etc. for labels, text, and backfill.

3.  I need to get element properties for box shapes, styles, fill info.

4.  I need to distinguqis "static text" to know labels from boxes, from lines, etc.

5.  I need to ID Radio Button Groups and buttons.

6.  I need to ID subforms on parent forms, and ID linkage information.

7.  I want to get lists of combo box hardcoded picklist values

8.  I want to get hardcoded initial values of elements where they exist.

This was just a partial list, running freely into my keyboard.

Perhaps there are some undocumented functions that can help provide me with some of this information?
(HINT: The correct answers should either be 1) "YES", or 2) I can test a beta version of 2.0 that will have those functions).

Quote:
Found them, right where they belong in the Programming Guide, with @ElementType(), pages 115-117.  Arrrgh!

Thanks for the suggestion to merge, but merging won't work in this case.  I actually need to merge froms, not just databases.  I am working with a design I inherited that has four different databases that should have been, and soon will be, just one database.  This will eliminate many duplicate entries, synching problems, and duplicative programming, report designs, etc.

But part of doing this is taking six individual forms, with tabbed pages and subforms, and putting them onto one combined form that is tabbed for each of the previous single forms.  Will be using conditional visibility on tabs and elements.  Ultimately many duplicate fields will go away, but for now, this will combine them.  Some duplicate elements will now become ReadOnly, and filled in by elements on other Tabs on this one form.  Want to maintain pixel positions, colors, etc. of existing elements on new Tabs.  End users should see same as now, but all in one database vs. multiples.

I have completed setting up one form manually on a new TabPage.  I then made that Tab the first one.  I was then able to easily import the records from the original database in the same order.  Did a Mass Update to the new records to ID them as imports from old database.  Now I will do the same with the next page, temporarily making it the first one to simplify the import specs.

So, now on to Tab2, adding one element at a time, then bringing in the programming for that original form, setting up the initial values, restrictions, combo lists, etc.  Only have another three to go. Arrrgh!

Not sure what you mean about contacting Lantica re using version 2.  Are you suggesting that if I provide some info, they may be able to generate the info I want in some type of file?  That is probably worth a phone call on Monday.  Certainly won't be done by then.

Thanks again for the suggestion.

Bob_Hansen wrote on Jun 17^th, 2006 at 6:53am:


Bob what modifications have you made to it?

Thanks