Cascading Updates suddenly fails???

[ChuckWhite]

Cascading updates suddenly stopped cascading. This behavior may have started after the installation of Access 2003. The problem relationship is between Client and Services tables using the Social Security #.

Application is client/server, built in ACC2000 and is still in that format of necessity.

Users have the necessary rights to the backend DB.

Open as Admin is set.

Access Security is not used. Well, used only in that the default MDW is created on each workstation by Access.

Backend DB relationships have Referential Integrity set with Cascade Update checked.

Frontend DB, using linked tables, has Referential Integrity checked but cascading is unchecked. The checkboxes are greyed out

Any ideas?

 

[dhookom]

The cascading would need to be set up on your server, not in Access.

Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]

 

[ChuckWhite]

Cascading is setup on the server.

Boy, do I feel stupid (bouncing heel of hand off forehead)!

Somehow Autocorrect was turned on in the backend DB which slowed Updates. Because of that we weren't waiting long enough. The cascade WAS happening, just veeeery slowly.

Thank you for your attention.

 

[dhookom]

Chuck,
Just one small correction. You stated "Application is client/server". This generally means your data resides on a database server such as SQL Server or Oracle. Some of your other statements suggest you have a split Access application with the back end on a "file server".

It's a small point but if you use "client/server", someone may make some incorrect assumptions regarding your system.

Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]