asked on

Local mdb file

We have an MS Access 2010 database on a server, and then on the local computers on the network
We have a Front end Access Database that's linked to the server,
what's the best way when I am making changes on the front end I shouldn't need to go all computers and
copy over the new mdb file, how can I do it from the server to copy over the new mdb file to all computers from the network.
Thanks in advance.
Frimy

ASKER CERTIFIED SOLUTION

Rey Obrero (Capricorn1)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

John Tsioumpris

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

PatHartman

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Jim Dettman (EE MVE)

To further the above comments a bit from Ray and John, Auto FE updater is well thought out, has a lot of features you need, and works extremely well. The price for it is more than fair, even though some might consider it high.

But as John pointed out, a simple file copy in a batch file is all you need. For many years, I used a setup like that.

What I'd do is have a version control table local to the FE (tblAppVersionControl). Then I would create a link to the same table in a "master" FE on the server (tblAppVersionControlNet).

I'd compare the Dmax() of the version field, and if they didn't match, would message the user that they needed to update. The "update" was nothing more than a shortcut to a batch file on the server. They'd execute, new FE would be copied down, and now the app would start because the versions would match.

Only down side; it wasn't "in-place". Users needed to exit the app and execute the short cut.

AutoFE works by the "launcher" method; a small .EXE starts first, does all the checks and what not, then starts up your DB. That method gives you a few more options in controlling things.

Jim.

PatHartman

The .bat file I posted works quite easily and doesn't ask the users to do anything. We also use one for our Citrix users (with different paths). The FE's of split databases (I hope you compact before you distribute) are small enough that they don't take more than a couple of seconds to download and open. The upside is that I never have to worry about the FE bloating or needing a CR. The users get a new copy at least once per day.

Gustav Brock

We use a method similar to Pat's. Zero trouble, zero cost, will never fail, always up-to-date frontend.

/gustav

Jim Dettman (EE MVE)

There are pro/cons to all of the approaches. The take away is that it's easy to do and you have a range of options for doing it.

Jim.

SOLUTION

aikimark

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

aikimark

Note: I also have a timer in a hidden file that looks for any change in the app version file name or the presence of a app stop file name out on the server.

frimy

ASKER

I've requested that this question be deleted for the following reason:

i found a solution

aikimark

@frimy

What was the solution that you found?

Jim Dettman (EE MVE)

Which is?

While it's great that you found a solution, it's even better when you come back and post it so everyone can learn.

So please post what you found worked, then select your own comment as answer.

Thanks,
Jim.

frimy

ASKER

I like you ALL,
My solution was to put it on hold for now.
I thought it's something simple.
But i see it will take time to test and implement it and we are very busy now.
Thanks again