No they're not that round, it was just an example.
Now all that is left in the system is records with record ID above 8134.
When they started using the solution first record ID was around 1000 or so.
How do you identify the RecordID - is it an auto-enter serial calc or the actual, real FileMaker -recid ?
So when the data loss happens, it always affects older record in blocks, I can affirm this because I see that the records that survived are perfectly sequential (8134, 8135 etc...).
True FileMaker -recids are not actually sequential, although they will appear to be for some large blocks, but I don't think this is the issue at hand
A little bit about the solution itself:
I have an Inventory table a Loan table and a Borrowed items table.
Inventory contains clothing items, when they get loaned the employee creates a loan, with basic info etc...and then adds items from inventory to the loan. This actually creates a line item that exists in the Borrowed Items table.
The records in the Borrowed Items are the one disappearing. No one can access the Borrowed Items table records directly. They're visible only inside a portal on the Loan layout and they can only deleted via button/script, one by one (no delete found records available).The script also logs who has deleted what and there's no record showing anyone deleting more than a few items here there(if they add items by mistake).
No record can be deleted via relation.
All of this sounds reasonable, but I would be double-checking every relationship into the BorrowedItems table to be certain there is no Delete Child allowed...
So I narrowed down this to:
Server Problems (Backup related, Server crash or memory problems or the server hitting his limit of databases/records being hosted).
Highly unlikely under most circumstances - all of these may lead to a corrupt database which requires repair, but not to records being removed.
Their IT guy messing up and trying to restore and reimport data after a crash (this though I will never know, because and I don't have access to the server...)
Thanks for your assistance!
This sounds more likely, especially if the record id you are talking about is a serial number of some sort.
One other thing - do you have an old copy of the database with old data - see if you can find a borrowed item that is actually the same as one in the current version in every respect except the record id (ie, same Inventory item, borrowed by the same person on the same date)...