bigzilla Posted February 15, 2005 Share Posted February 15, 2005 What in the world is happening. My database is set to "Show all Records" and I'm scrolling thru them one by one looking for specific records to Delete. I find one and go up to the Records menu and select "Delete Record" Not "Delete ALL Records", "Delete Record"! A dialog box come forward "Permanently delete ENTIRE record" and I select Delete. Guess what. It Deleted ALL RECORDS! I thought, well, I must have selected "Delete ALL Records" by mistake. So I duplicated a file and did the same thing, making sure I selected "Delete Record" and the same thing happened, it deleted all records. What can I do to stop this. I even downloaded a trial version of 7 today thinking something may be wrong with mine. But it does the same thing. Is there something I'm doing wrong? Bill Link to comment Share on other sites More sharing options...
bikergeek Posted February 15, 2005 Share Posted February 15, 2005 Do you have a portal with 'delete related records' enabled? A friend commented that he was having the same problem. Maybe rebuilding the layout will fix it. (If so, it suggests corruption.) Link to comment Share on other sites More sharing options...
J Wenmeekers Posted February 15, 2005 Share Posted February 15, 2005 Better look for a self join-relatioinship with delete records allowed.... Link to comment Share on other sites More sharing options...
bigzilla Posted February 15, 2005 Author Share Posted February 15, 2005 Hi J.W, That did it. I did have a self join-relationship (3 of them) and when I unchecked delete records allowed, it took care of it. I must say that I'm very surprised that FileMaker would allow "Delete Record" to be selected, then allow the deletion of all records, when clearly that was not what was selected! It's like the car manual says "You cannot start your car without a key"! But you find out later from a mechanic that you can start the car without a key “if you have the glove box open with the interior light on"! Very strange and it scares me a little to wonder what other anomalies there are that we may not find out about until we have a bunch of different processors working within the system! Wow! Bill Link to comment Share on other sites More sharing options...
Leader Posted February 15, 2005 Share Posted February 15, 2005 (dryly) It sounds more like 'shut of your engine with key' and it blows up. Link to comment Share on other sites More sharing options...
-Queue- Posted February 15, 2005 Share Posted February 15, 2005 It does make sense though, if you have a self-join relationship to other records in the table/file with 'delete related records' selected. It's no different than a parent-child relationship to another table/file with 'delete' enabled. You delete the parent, and the the child records are deleted. In a self-join instance, the parent may also be the child and/or all other records in the file/table may be children. Cascading deletes such as this can be quite useful, but you have to be careful to avoid using them incorrectly. Link to comment Share on other sites More sharing options...
J Wenmeekers Posted February 15, 2005 Share Posted February 15, 2005 Allways script your 'delete'to delete records through the relationship. Build an allert in the script, something like: filename = filename, with a message; at least two allert messages that all the records will be deleted... Not 100%, but if the user still deletes all the records after two allert messages, it's a PIBKAC... Link to comment Share on other sites More sharing options...
By Soliant Consulting,
By Soliant Consulting,
By Soliant Consulting,
Recommended Posts
Archived
This topic is now archived and is closed to further replies.