Database Sharing...

[nigeve]

Gentlemen, I have developed a database that needs to be used by up to 30 people (but probably no more and 2 or 3 at the same time). It has a front/back end split. However, I am unable to install the front end on the users PCs (No privileges) so the FE.mdb and the BE.mdb sit on the network. All the users PC’s have shorts cuts to the same FE on the network.
It all seems to work fine but will there be any problems lurking around the corner..?
Additionally, they all have Access runtime only so I have left the front end as an mdb.
Many thanks

 

[spikepl]

I am unable to install the front end on the users PCs (No privileges)

You are sure? In that an Access database is NOT an executable application as such but a data file, especially an .mde or .accde runnable in RUntime only, almost on par with a .docx or .xslx, and does not require "installation" but just being put somewhere on the user's drive.

 

[George21]

Yoy should make fe.mde and copy it to "My Documents" (or any other folder in the profile of each user) in their PC. Make sure that the linked tables are correctly rooted in the server.

 

[nigeve]

Gizmo, Spikepl, I am working for a government department where people are just too inept or lazy to copy the front end into their own my documents. I could do it myself for them but they all have individual logons, work various shifts across a 24 hour period from many different offices.
I guess I could try to get a senior manager to insist they do this. I think it would be easier than having individual copies for each user on the server with a short cut. I guess creating an mde with some version checking in the code would work, then the users could be prompted to copy the latest version into their documents folder every time there is a new release.
George, yes agree about the correct way to use server path. I am using some code and FE tables to connect to the back end so will correctly list the db location in the table field instead of using d:\...

Thanks for your comments…​