We'll keep that in mind. Currently, all our tables are free tables. We've stayed away from DBCs. However, that may be a quicker, short term solution.

Thanks
>One suggestion by Ed Leafe in the CodeBook forum.
>
>----Begin quote----
>If they are in a DBC, you can add triggers that will fail if a certain public memvar doesn't exist. In your app, set that memvar at startup, and release it at cleanup. This way, all inserts, updates and deletions will fail unless they happen from within your app.
>_________________
>-- Ed
>----End quote----
>
>>We currently have a Novell file server. In order for our users to be able to run our software (and in turn view and edit our tables on Novell) we have had to give our users read/write permissions on our tables.
>>
>>However, this also enables any user to simply open any of our tables using Access or Excel.
>>
>>We're just now beginning to look into alternatives. Migrating to a SQL Server backend would be a HUGE undertaking for us at this point in time. Are there smaller steps that can be taken to secure our files from being tampered with except via the code we write?
>>
>>Grateful for any ideas!
>>
>>P.S. As a side note, we are slowly moving away from Novell and have started some changes that will allow us to move to a Microsoft file server rather than Novell.