Dictionary

[Fletch]

Coming from another PC based RDBMS, I relied on table dictionaries. AV doesn't have one built in, so I created & use dictionaries. At the suggestion of Tom Cone, I am posting this trick I use. I am naturally a bit lazy and can never remember exactly what I called a certain field in that other table. So to help me, I create a single table and use it as a dictionary.

Call it "Mast_Dict". In this table, I create all fields that will be used in every other table. If I am adding a field I add it here first. For example if I expect to have 5 tables with say 50 fields, all the fields get created here first. I do not put in field rules. The Mast_Dict is used to help me keep my field names, field types, field lengths, etc.... the same throughout the application.

Once complete, I save the Mast_Dict. To create my first table, I open Mast_Dict in Design mode and re-save as "Customers". Now I open Customers in design mode and delete the fields that will not be used in this table. To create additional tables, I repeat this same procedure; saving under a different name and deleting different fields.

If a new field needs to be added to Customers, I add the field in Mast_Dict and then copy to Customers.

I imagine the same thing could be done for forms or browse modes.

[Cheryl Lemire]

Hi Fletch,

I would not call you 'lazy', you simply choose to use your time more effectively. I follow a similar approach. I hava a 'master' table where I keep fields that I have standard in all my tables: id, processer, date_ent, time_ent, proc_mod, date_mod, and time_mod. Since these fields all have special entries in the field rules, I populate these as well: Field Desc, Data Entry, Transitions, Record Events.

Whenever I create a new table, I create it by copying my 'master' table. I then go in and change the field name of 'id' to be specific to the new table. The only changes I need to make in the field rules is in the Record Events where I need to change the name of my 'id' field again.

For tables that store similar data, ie customers, vendors, manufacturers (names, addresses, phone numbers) I create the first table say 'customers' from my 'master' table, make the necessary 'id' changes and then add the name, address, phone, etc fields that I need. I then use my 'customers' table and copy it to create the vendors and manufacturers tables.

I imagine the same thing could be done for forms or browse modes.

I do the same thing with my forms. In my most recent application I use menu's and add/edit forms throughout the application. I have a master menu and a master add/edit form. There are several form events, button locations and events, titles, logos, an embedded browse (add/edit forms), etc.

I normally create my main menu first with all the form events and objects, code them accordingly. Once it is the way I want it and functioning, I copy it and name it 'master_menu'. I do the same with my first add/edit form, getting it functioning the way I want it, I copy it and name it 'master_addedit'. Whenever I am ready to create a new menu or add/edit form, I take the master form and copy it to the desired table. Now all I have to do is add the appropriate fields.

Anyway, just wanted to pat you on the back for sharing your idea and let you know that you are not 'lazy', just intuitive.

Good luck
Cheryl

[Fletch]

Cheryl

Lazy people by nature, are intuitive. There has to be a quicker, simplier, easier way to do things. Just some of my lazy cohorts never get past the dreaming stage and onto the getting it done stage.