Printable View
1. Is there a way to have multiple users log into a program driven by access. Bypassing the lockfile and not getting the open table error.
2. What would be the best way to make a number "autonumber" without using the autonumber function in access. I'm making a small purchase order program for a company and they need purchase orders starting at 1467. Right now i'm using an ini file but is there an easier way? and if two users are on simutaineously?
Yes. You can. But Access may not sustain for many users.Quote:
Originally Posted by trinic
I used have a separate table to generate auto number.Quote:
2. What would be the best way to make a number "autonumber" without using the autonumber function in access. I'm making a small purchase order program for a company and they need purchase orders starting at 1467. Right now i'm using an ini file but is there an easier way? and if two users are on simutaineously?
The issues that you will (and I say "will" not "may") encounter with multiple users loging into a netword Access application is really dependent not on the number of users but the number of concurrent users. How many people will be accessing this application at the same time? (Best guess?)
no more than 4
Simpl create an autonumber field, and add a dummy record with an ID of 1466 (I think you can delete it once created). The next number created for the autonumber field will be 1467.Quote:
..they need purchase orders starting at 1467. ...
Do not use autonumber
At the time of inserting record just find ouit maximum number from database and make it increament by 1. if there is no record in database then start it from 1467
With no more than 4 concurrent users, you shouldn't have too much of an issue with a networked Access application.Quote:
Originally Posted by trinic
Access starts to not play nice when you get into the double digit concurrent users.
I strongly disagree I'm afraid.. As there are multiple concurrent users, it is possible that more than one person will try to create a record at the same time.Quote:
Originally Posted by mvirendra
If you are generating the number within your program (or even within an SQL statement) then you create the opportunity for multiple records to have the same ID, which can cause several issues with data and the application(s) that work with it. Using an autonumber will eliminate this possibility.
If this were a single user system, then generating the numbers yourself would an option.