Split DB configuration issue

[PaulA]

Hi, all -

I'm an offsite administrator of an Access 2013 database with the backend on a shared server and each user with a front end on his or her hard drive.

We this arrangement has worked but has become more complicated with the site using the DB having users working from perhaps more than one workstation and a change of workstation being possible at any time. The site IT people have set up the arrangement so that a person can log on to their main account from any computer.

However, the front end DB needs to be installed on each user's hard drive on each computer they work on, which can get complicated, especially when I'm off site.

I was wondering about going back to a shared access front end DB housed on the shared drive so this won't matter. I'm assuming this would result in slower functioning of the application, especially as there are many more users now from when the DB was first developed.

Would anyone have any thoughts on ways of addressing this complexity of our set up?

Thanks!

 

[Ranman256]

It should NOT be complicated.
All you have to do is copy/paste the FE to the working PC.
And it will work.

 

[Simon_MT]

Oddly, A Terminal Server does precisely that with a long Session Timeout. Each user has a Front End and can use this account remotely as well. If that swap PCs the Session will be resumed and previous instance dropped.

Simon

 

[CJ_London]

I was wondering about going back to a shared access front end DB housed on the shared drive so this won't matter. I'm assuming this would result in slower functioning of the application, especially as there are many more users now from when the DB was first developed.

it is also likely to result in corruption of the front end

The site IT people have set up the arrangement so that a person can log on to their main account from any computer.

needs a bit of clarification, but this implies they have access to their mydocs and desktop - so you should be able to put the individual front ends there.