Splitting of MS Access program for LAN

[rehanemis]

Hello,

I have simple program and want to split it for other users to use it on LAN.
So each user can use the same form at a time?

suppose Mr. A using "Form1" and working on transaction ID=1 and Mr. B also opened the "Form1" and working on Transaction ID=2. When both hit the print invoice button the invoice going to print using query which takes Transaction ID from the "Form1". Can they print their own Invoice?

any advice?

 

[moke123]

Yes they can use the same form, sort of. They will actually be using a separate instance of the same form as the front end file needs to be installed on each users machine.

heres a link to a good write up on splitting a Db.
http://www.fmsinc.com/microsoftaccess/databasesplitter/

 

[The_Doc_Man]

rehanemis, the splitting of the database into a front-end (FE) and back-end (BE) is actually the suggested or preferred way to do what you wanted to do.

The reason you want the FE files on each individual computer is file locking. If you have one great big file with everything in it, people will sometimes be likely to step over each other, particularly if there is one form that is more popular than the others. But if the FE files are separate and everyone has a private copy, the locking for that part of the database is all local to the user's system and therefore not visible to others. I.e. not nearly so many lock collisions or conflicts.

If you then assure that you have optimistic locking for everything that can update the BE content, you have done a large part towards helping your users to do things in the most efficient way.

There is more to it than that, of course. Search this forum for topics such as "Splitting a database" and "Securing a database" to find many questions that might be helpful on the topic of making your database work for your users.