Yes, I saw your reply to my original post:
1) I've tested it with around 80,000 records but, as the number of records grows, it's slower to load the file. The largest database that I, personally, use it with has a few thousand records.
***** I will probably use it for less than 10,000 records, so this is good.
2/3) Sure, a single user could store the files on a network share (I do that with mine). That said, I wouldn't recommend using it simultaneously in a shared environment as Snap DB is not multi-user aware whatsoever
***** We use Excel right now (setup as one tab per part number, which is really not working, as we add a lot of new part numbers), which does lock the file so a second user gets read only mode. But SnapDB is so much simpler and has better search and data entry I would like to use it if possible.
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.
Any suspected problems I need to test for in using with multiple users on a network?
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?