< CRINGE! > If those triggers/rules are looking for variables or objects created by the app, they will certainly fail. As a general practice, I do everything I can to prevent users from modifying any data unless they access it via the method of my choice. No hacking allowed.

>We have an app with a .dbc and tables that a client wants to link up to using Access and view the tables and occasionally modify data. Viewing the data using ODBC is not a problem until the client tries to modify a field in a table that has triggers/rules applied to it. Can you tell me why or why not this works? I am a little ODBC slow when hooking to Fox. How would I remedy this? Do I make a COM object that they talk to with Access or is there other methods?
>
>Thanks,
>
>Michael