Split Access 2010 database can I relink remotely

[Bursal]

Is there a way I can relink a split database frontend and backend remotely?

My situation is I am a volunteer with a community organisation and I administer their Access 2010 database, which is a ‘work in progress’. The database is split and the backend is stored on a server running WS2013E and the frontend is on workers computers. My problem is I live about an hour’s drive from the office so I am not on hand to do any modifications.

My current procedure for any modifications is let the staff know that the database is ‘read only’ so no new data is to be added, I download the front and backends using Remote Web Access, join them and do the modifications and then when I can get to the office split the database and load onto the server. That's fine if I am only going to be a day or so but sometimes it is over a week. I use a version numbering system so that I can ensure everyone has the latest version.

I would like to be able to split the database at home, upload the front and backends and then relink them. Is this possible? One problem is I am not very good with code but I am happy to try but I may need to ask seemly dumb questions.

Thanks
Di

 

[Rx_]

Lets break this down.
The Workers (workstations) are on a LAN at the office?
You are remote, workers are at the office?
The back-end DB is what ? (MS Access, SQL Server, other..)

Here is an example of a solution:
Local Table on the front-end listing tables on back-end to be linked
Code, deletes all linked tables - then uses Local Table to create Linked Tables.
(Same code with different path info - allows developer to link to local copy)
One Location on LAN to post current version of Front-end.
Run - table linking code in that folder (now current version is linked)
Bat File - User runs shortcut to bat file
- Makes copy of Current version, copies Current Version (front end) to users workstation.

This way, it reduces the effort for distributing a new release.

 

[Bursal]

Thanks for the reply Rx.

The workstations are on a LAN in the one location and the backend is Access 2010. I would make changes at weekends and only when there no one is in the office.

The solution sounds just what I need but when it comes to code and bat files I have no idea. I don't mind learning and trying but can you suggest a starting point for me.

Thanks
Di

 

[Rx_]

The code makes a directory in the user's home directory and then copies the file over and then starts it. So basically, the developer puts out one single copy of the Access Front End. When the user request it, the user gets a copy of that put into their personal User folder.
This way, each of the many users have a Front-End.
This is what works on the network drive to get you started.

@echo Please wait while a copy of the Access DB Front End is copied to your individual users folder.
@echo off

MD "L:\Database\"
xcopy /Q /Y R:\FE\Current\TaxAuditAssignments.mde "L:\Database\*.*"
TYPE NUL | choice /c:delay /td,5 >NUL
Start /max "E:\Microsoft Office\OFFICE11\MSACCESS.EXE" "L:\Database\TaxAuditAssignments.mde"

exit

 

[spikepl]

The simplest method of all is to set up a "mirror" of their server disk name on your computer: so, eg, if the backend on their sever is in H:/Shared Files/Access Stuff/ Bla bla/AcessBackend.Accdb

then you set up a directory on your computer as a drive of the same name. Then you do your relinking at home once and for all, and each copy of your front end is good to go, both at your place and theirs.

 

[Bursal]

Thanks Rx and spikepl,

I like spikepl's solution because it is simple so I will start there and see how I go.

Thanks to both of you for taking the time to answer my post.
Di