How to Run MS Access 2013 DB on LAN

[rehanemis]

HI,

I have developed an ms access program having tables, forms, queries, macro and some vba code. I would like to run application over LAN for 3-4 computers along with different User rights. Suppose, Manager can View Reports at any time on his computer, Data entry Operator view(for data entry entry only), Technician View(to View his record entered by data entry operator) and Administrator view( who is responsible to make any changes, updating, maintenance in ms access program. Can view whole activities).

I am using ms access 2013 version. Computers are connected through LAN.

I am new to this type of application running over LAN.

Please advice me how can i implement it.

Note: I can make login screen for different users to enter and can work on his own authentications) but don't know how to run over LAN.

Thanks and looking forward to hearing from you(experts) soon.

 

[pbaldy]

Note: I can make login screen for different users to enter and can work on his own authentications) but don't know how to run over LAN.

It shouldn't be any different over a LAN, other than the db should be split:

http://www.kallal.ca/Articles/split/

 

[Steve R.]

As pbaldy recommends, the database must be split. However, for your back-end, I would encourage the use a free open source database such as (MYSQL, Maria, Firebird, or HSQLDB. Even SQL Server Express would be a possibility.

The reason for making that suggestion is that in my one experience with MS Access as a back-end on a LAN - was that it proved to be sluggish and some records were periodically lost. Moving the back-ed to MS SQL Server resolved those issues. You may not have those issues.

Note: Concerning the databases mentioned above, I do not have sufficient knowledge for making any recommendations concerning which would be better.

 

[rehanemis]

Thanks pbaldy and Steve R..

Mr.Steve R. I don't know how to use MySql or Sql Server Express as back end. Can you more guide me or give me link of tutorial to do so and also for front end to develop.

Thanks

 

[Steve R.]

Due to a lack of experience, I can make no recommendations concerning other databases or to suggest any tutorials. What I can say is that I have MySQL set-up as the back-end (on a home LAN) to an MS Access front-end and it works just great.

 

[rehanemis]

Thank you very much.

 

[jdcallejas]

Hello,

I have created a database and for some reason I can’t run it on my network. I have splitted the database, I have the BE on a server and each pc has its own FE, forms, query and reports. When I link the tables I LINK all the tables, I am able to see the records, go to next, previous, first and last, but when I want to add a new record it says "You can’t go to the specific record".

I read the http://www.kallal.ca/Articles/split/. I am familiar with access and I have done the procedure of splitting a database in MS Access 2003. I didn’t have any problems; this was back in 2001 or 2002.

Anyway I tried to save as MDE file but in Access 2010 its call ACCDE. When I tried to do the whole FE with all the forms it said that it was too large, so I did each department FE individual and it was able to save it.

When I ran it on the remote PC, none of the VB coded buttons worked, example: Docmd.openform or Docmd.Close. I created a new buttons to test with the default macro and it worked. I checked the VB Module and it was empty. Looks like to me that is not importing the VB code when I save it as ACCDE.
I don’t remember exactly if I saved the 2003 database as .mde back in 2002, so I wanted to test to see if my problem on the network consisted on not saving it as ACCDE.

I am open to any suggestions; I have been working on this problem for weeks...

If you need me to upload the DB please let me know.

Thank you.

 

[GinaWhipp]

There are a couple of things you can check first...

References...
http://www.access-diva.com/d5.html

Trusted Locations (new since Access 2007)...
http://www.access-diva.com/d4.html

Then Compact and Repair and re-split. Side note, creating an ACCDE removes all the code. If that is not your intention then leave as an .ACCDB. Also, note, when linking everyone must have the same path to the linked tables.