Networked front end back end?

[bluenose76]

Gentlemen,

I have a single database that I would like many people to use concurrently. The db will be stored on a security clamped network with my users logging on with there own individually user accounts.

Does anybody know the simplest way of creating a distributable user front end that would allow simultaneous use by many people?

Any and all advise is greatly appreciated.

 

[Rabbie]

Bob Larson has developed a system for managing distributable FE. Try a search on this forum for more info. Sorry I don't have the link handy

 

[Phonik]

Hi

The way I do this is simply build your database in one file initially, including all your forms and queries. Then when you are ready simply create another empty database and name it server.mbd. Then, copy all the tables from your completed database into the new one. DO NOT LINK THEM. Once you have all your tables in the server database, return to your first database, which I call the client, and create linked tables to all the tables that sit in your sever database. Note here that the path you chose to link them must be the same as the path that the users will have available. e.g If you store the database on a network drive path S:\Database, you must make sure your users have this path too or the linked tables wont work.
I then store both the client and server databases in the network folder. I leave the client there to do development work on. What I then do is I create a MS dos batch file that is sent out in an email to all new users of the database. The batch file enters the network folder and copies the client database onto the users C:.
Providing you have worked through correctly, all the tables in the client database on the users machine will all point to the network server database.
This is known to many as a relational structure/database and is the most common way of running a database. The speed will really depend on how fast your network is and the size of the server database. Let me know if you get stuck.

Gareth

 

[Rabbie]

If you link using UNC links as reccommended in several posts on this forum then it will still work regardless of how each user has mapped their drives.

 

[bluenose76]

Phonic, Rabbie,

Thank you for your guidance, I shall try the UNC version as my network is a security clamped design that I personally have little controll over.

All going well this will work?

By doing this, will there be any limitations to the ammount of users I can have accesesing the db at any one time?

I shall let you all know how I get on

 

[bluenose76]

Gentlmen.
I am sorry for not replying sooner, I wanted to inform you that i have implemented the UNC Path and my db is working fine.

I now have my FE / BE working fine, although a little slow but this i beleive is due toi my network and not the db.

thank you once again for your help.

regards
Bev

 

[boblarson]

As mentioned in an earlier post, I have a tool that will let you enable auto updating for your frontend. This means you can make changes to a master and just by changing the version numbers your users will, the next time they open the database, get a message that their frontend is out-of-date and then it will close, delete the old file, copy the new file from your master location, and then reopen automatically for them.

You can get it free in the samples category on the forum or by going here:
http://www.btabdevelopment.com/main/AccessTools/tabid/78/Default.aspx