Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / October 2004

Tip: Looking for answers? Try searching our database.

Cascade Delete Warning Not Happening

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ed Ardzinski - 04 Oct 2004 18:09 GMT
I'm working on a database in A2K, FE/BE design...all pretty much standard.  
The main data table is related to several child tables, with 1 to many
relationships, RI enforced and cascade deletes enabled.

I was getting the message about deleting child records previous to today.  I
rember clearly it happening, and my documentation has a screen shot of the
message box.  Now, after adding another table to be related to the PK of the
main table (I think this makes 4 child tables) the only message I get when
deleting a record in the main table that has children is the "You are about
to delete one record" rather than the more verbose message regarding the
deletion of children.

So far I have tried just about everything I can think of: deleted and
recreated the relationships in the BE, refreshed the table linkages in the
FE, created a new blank DB and imported everything in from the BE...still
when I delete the parent I get only the "You are about to delete 1 record"...

I also created a test of the cascading deletions with a couple of new
tables, doing the basics of relating them and enabling the cascading
deletes...and the test works fin, even with multiple child tables to the new
test parent table.  So I'm stumped as to why I suddenly lost the more
detailed warning on my main table.

BTW, the cascading delete still works on the parent table, I'm just not
getting the "correct" warning message.  Any ideas would be appreciated.

Thanks!
Ed Ardzinski - 06 Oct 2004 19:11 GMT
OK, for anyone who might find this in the future...

I found through trial and error that the issue was related to trying to
enforce RI between two child tables.  When I removed the relationship between
the child tables (which already had code written to deal with the issues) I
began to get the correct message from Access.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.