>>>>>Are there any disadvantages to encryting the OBJECTTYPE and/or OBJECTNAME fields in a .dbc? If you do this it will not allow the database to be opened by Excel or Access but I would like to get some opinions on the downside of doing this.
>>>>>
>>>>>TIA,
>>>>
>>>>Out of curiosity, how do you plan on having VFP read them after you have encrypted them?
>>>
>>>Within the app, having them programmatically unencrypted.
>>
>>But VFP uses these fields internally, and as far as I know doesn't give you a chance to get in between it and the dbc to do any decrypting. For example, when you USE a table that is a member of a dbc, VFP opens the dbc and reads its fields automatically.
>
>If you open the dbc before opening any tables, it is possible. That's how I have it working now. When the app first runs, it uses the dbc, runs the decryption routine, closes the dbc, and then opens the required tables. On logout, it checks to see if any users are on the system and if there aren't any users still on the system and if there aren't, closes all open tables, then the database, uses the database, encrypts it, and exits the app. I'm still testing it but it works fine so far.

So Access and Excel _can_ use the tables when somebody else is in the system...