Hi Bob.

>WHY... well, we allow the user to modify the database so that they can customize the system. We need a tool to do it to allow for the data dictionary to stay updated. In our 2.6 product, we wrote the tool, but everyone told use to go with SDT this time.

Would my answer to your other related message ("Update ideas") take care of this? If not, you've got a couple of choices:

1. Create a simplistic front end to the data dictionary.

Do you *really* want users using a tool as powerful as SDT's Database Explorer? I sure wouldn't. What you really want is to allow users to create new fields. Fine -- create a form that allows them to enter minimal information about a new field and then use ALTER TABLE to add the new field to their table. You can then use the SDT Validate method to update the meta data for that field.

2. Have them purchase SDT.

You could do this a couple of ways: have them purchase SDT outright themselves to do this task or have "Standard" and "Professional" versions of your app. With the professional version, they get a license of SDT (which you purchase from us).

Since this is the first time this has come up in the several years SDT has been available, I'm on new ground here. Do either of these approaches sound reasonable?

Doug