***** I will probably use it for less than 10,000 records, so this is good.
You should be fine with this number of records.
A quick check did not show any bad results from 2 users accessing at the same time. If they both were on the same record, the last one 2 save or change seems to be the one that had the data recorded his way. It is unlikely my users would be on the same record.
Keep in mind that Snap DB doesn't have any concept of saving individual records, i.e., it's a single flat file. That single SNP file gets written, in full, each time you save it. You have to think of this like two people having the same text file open. Both can open the file and make independent changes but the last person to save will overwrite any and all changes made previously by either person. Does that make sense?
Any suspected problems I need to test for in using with multiple users on a network?
Yes, what I just described above.
Any chance of using some simple form of file locking (of the database file on the server) which starts for the first user to open the file?
No, since I feel that's out of design scope for this app. I didn't design it, at all, with the idea of supporting multiple users.
If I seem unreceptive to the idea of your multiple-user scenario, I apologise. I'm just trying to let you know that you're going to run into trouble if you allow multiple users to modify an SNP file at the same time. If you simply plan to allow multiple users to use the database for lookups, that is, no modifications, you should be okay.
Logged
) is definitely a better solution!