In Add mode,  imported 350 records each containing about 5 subrecords, using sbasic.

Worked great. I then hit f7 to search through my new records, which opened a new tab. (Add mode is still open showing 350 records.)

In Search mode I did a few searches then mass deleted 24 records.(Add mode still open on 1st tab, probably showing 350 records)

Another user was searching for a record that I had just imported. It appeared that we landed on the same record because I saw "locked" show up on my screen. I tried to exit search mode, then the screen started flashing repeatedly (working, updating, working, updating). It looked like we were heading for a crash so I hit esc a few times and it quit to main tree. Other user was able to close sesame and exit.

I re-entered search mode, and checked my newly imported records. The 24 I deleted are gone, but also 29 parent records are missing, and the first parent record now shows 300+ SUBRECORDS with odd data (some random and some from the new parent forms) 'crammed' into various fields.

I went into the subrecord database to mass delete these strange records, and I cant find them.

It SEEMS like the subrecords were created automatically, OR the first subrecords just grabbed the 'relationships' for ALL the new parent records. I think this happened because I had ADD mode open while I mass deleted (and another user was in the db).

I'm trying to mass delete all these new imported records, but sesame keeps crashing. (One subrecord shows locked and read only, but all users are out and sesame server has been restarted several times.)

I deleted all the subrecords I COULD find, but still cant delete the parent records (server closes, or client crashes).

I'm sending to tech support to 'fix' and 'clean out stray records'. All subrecords in form Variants should be relational.

Thanks,
Steve

I'd like to see it. I'd also like to see the log file from the Server.

Quote:


No, but you did also restore the matching .dat also, right?

Quote:

No.

Quote:


Both. Each log file represents the messages for a Sesame session(s). Whenever you run Sesame as Client or as Server from a particular working directory, that working directory will get its own log file (which can be very handy!). In this case, I'd like to see both log files, so I can see the 'conversation' the Client and Server had with each other.
Can you tell me around what date and time of day the Mass Update occured? It will help me find the right spot in the logs.