Multiple users updating a form concurrently 1

[dmeyring]

Is it possible to have multiple users in the same database updating the same form concurrently? What if the form uses auto-numbering? If this produces any type of error, is it possible to have a notify window pop-up if another user is already in the form?

 

[Remou]

There are a number of things you should do if you have multiple users. To start, you should split the database. You may also wish to look at MichaelRed's FAQ on autonumbers. How much you need to do will depend on the number of concurrent users.

 

[dmeyring]

I have 2-3 concurrent users, it is typically 2, but the possibility exists for 3.

 

[Remou]

It is quite possible you will get away with autonumber in that case, unless a great many records are being created. However, do split you databse into a front-end and a back-end.

 

[Tarnish]

I got the impression that the autonumber doesn't 'calculate' until the instant the record is saved. I'm using autonumber in several of my tables so this is a concern.

I also read that you can choose between sequential and random for autonumbers. In reference to "random", the discussion was about using it when you have more than one copy of your database in use (but not setup with replication) and you'll be combining the records of them together at some point.

Maybe, in a multiuser environment, it would be better to use that option (random) than the sequential. If what I said about the timing is true, it seems practically impossible that two records would be saved simultaneously AND randomly use the same id number.

My app will have around 10 users. I'd like to here any more opinions or feedback based on experience about using autonumbers in a multiuser environment (and/or correct me if the above is erroneous).

Thanks,
T

 

[Remou]

I think a lot depends on the way that new records are created. For example, if an unbound form is used to collect the essential information and the new record is created from this form, there will be little or no delay in creating the record and therefore less chance of conflict. If ten users are working furiously creating records, I think it would be wise to read this:
Why AutoNumber shouldn't be used in MultiUser databases (And How to ge the Unique Number)
faq700-184
If the ten users are creating a record from time to time, you may get away with autonumber.