Multiple Users

[alyon]

I know you can split a database to make it available to multiple users. I also have it located in a network folder. But, the problem is that when two people are entering in the program, only one can save. Is there a way to fix this? Or, if I were to create two new programs off one table (I'm not even sure that's possible -- but I think it is) .. would one person be able to work in one program, and the other in the other program?




Thanks for the help,
alyon

[John_G]

I assume you have split the database? But have you put BOTH front end (forms, queries etc.) and back end (data) on the network? If so, that is your problem, I think - all users are are running the same front end, and that leads to all sorts of trouble.

Each user should have a copy of the front end on their own machines, with all those copies linked to the same back end on the network.

If you are set up this way, there is something else going on. What do you mean by "only one person can save"? - only one can create new records, or only one can update?

John

[June7]

This thread describes how I manage a split db with multiple users http://forums.aspfree.com/microsoft-...ue-323364.html

[alyon]

John, yes, I do have the the database split, but yes I have both front end and back end on the network -- which would definitely be my problem as to why they can't save or update-- I didn't even think of that until now! :x But, the problem is-- I'm constantly having to edit the form -- add buttons, change the reports, etc., so if every user puts the front end on their own computers... won't I have to edit each person's individual form? However, if I'm understanding correctly June, isn't this what your second code takes care of?

Thank you both for your help!
alyon

[John_G]

Hi -

You would not have to modify each copy of the front end individually. Just put a copy of the latest front end .mdb on the network, and have the users (or do it for them) replace their version with the updated one. This is the easiest approach (IMO), but it can be tricky if there are temporary "working" tables in the front end.

There are ways of automating this process - one is called AutoUpdate (I think!) - can another user please post the link - I don't have it.


John

[alyon]

That would work! Thanks!