Access 2003, cascading updates fail for users

C

CWDev

In Access 2003, why do cascading updates work for the developer and not for
users? This behavior (likely) began upon installation of Office 2003, though
the DB is in Office 2000 format.

The implementation is client server.
Users have full rights to the folder containing the backend.
Linked backend tables show relationships with referential integrity checked
but grayed out and cascading options are not checked.
In the backend DB, cascading is selected.
Access security is not used.

Any thoughts?
 
M

[MVP] S.Clark

Did you check that the Cascade updates checkbox is still checked for that
relationship?
Sorry to ask the obvious, but it is the first place to start.

Also, there is no "Client Server" setup with Access Jet tables. It's just
split databases. Client Server would be using SQL Server, MSDE, or other
such server.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Occasional crash when deleting a record 4
Records currently locked by another session? 0
Joins & Cascading 4
referential integrity selected but cascade delete is greyed out 3
Developing a new DB; Organization, Relationships, Cascade Update.. 6
How to enforce cascade update/delete? 3
Cascading updates fail for users but work for Admin 0
cascade delete warning 3

Top