Under Record Menu
Delete Record... Ctrl+E
Delete All Records
If Control+E deletes all records, or the menu selection deletes all.
There is a dim possibility that the database is corrupt, I have never seen this symptom.
1] Save as smaller
2] Open SavedAsSmaller copy and Save as Clone, import records from the original and test.
Unlikely to solve the problem, but is a quick test.
Or another remote possibility is that you have a customised menu attached to the layout, and the 'Delete Record' menu has been changed to actually implement 'Delete All'.
Also check the relationship and see if 'allow deletion of related' is checked. If Cartesian and self-join, all records would be deleted when current record is deleted.
Yes, 'alllow deletion of related' in a self join was checked. I unchecked and the Delete Record icon behaved correctly However, the database copy that behaved
properly also had' deletion of related' checked - (and the same self join) so more testing to do later on today. I would lik e to know WHY.
It would depend upon the keys involved in that relationship. One primary record might have only one related in which case only one 'related' record would delete. But if its relational key matches more than one self-join record, it can delete more than one. Without seeing the file, we could not say more.
Good luck on pinning it down; I know how it can be when the unexplained happens. :^)
My thanks for all the advice, but I am having to put this problem on the back burner. it appears that some part of the program is corrupt as I am now having lock-ups when editing scripts. The other copy is working properly. I would like to find out why/what is happening, but need to get the database up and running to meet a user's deadline. I hope to come back to sort this out at some time in the future.
To close off this query, I could not find any errors or oddities in the parts of the program accessible to myself, but based on the advice received earlier, I looked
very hard at the relationships. So, the relationships on the Graph were deleted and replaced with identical relationships. The problem has gone away. Guess
it was something corrupt in the related software and not apparent to me.