Distributing runtime version of Access DB on a network

[Craig]

Hello,

I have an Access 2003 database that is split into two parts: HR Front
End.mdb and HR Back End.mdb. There is a third file, Security.mdw, which
determines user-level security for the whole thing.

As very few people will be using this database (it is designed for an HR
department of about six people), I want to put both the front end and the
back end on the network. That way, when I make updates to the front end, I
can overwrite HR Front End.mdb and everyone will get the changes instantly,
rather than the end-users having to install an update.

Not all end users have MS Access, so I am using the Packaging Wizard to
distribute the runtime version.

My questions:

1. Is there a way to distribute the runtime version only? So far, from what
I can see, it looks like you have to package an Access DB file with it. I
would like to be able to distribute the runtime "engine" alone, and then have
people follow a shortcut to the network file.

2. If I have to package a file with it, is there any way I can get the
package to point to the HR Front End.mdb on the network? So far, from what I
can see, it looks like the packaging wizard installs a file to the user's PC.
Likewise for the security file, Security.mdw --- I want the users to always
be referencing the copy on the network.

Hopefully it is clear what I am trying to do --- or, if this is not the most
elegant solution, can someone offer an alternative?

Thanks for all your help!

Craig

 

[John W. Vinson]

Hello,

I have an Access 2003 database that is split into two parts: HR Front
End.mdb and HR Back End.mdb. There is a third file, Security.mdw, which
determines user-level security for the whole thing.

As very few people will be using this database (it is designed for an HR
department of about six people), I want to put both the front end and the
back end on the network. That way, when I make updates to the front end, I
can overwrite HR Front End.mdb and everyone will get the changes instantly,
rather than the end-users having to install an update.

That's a Very Bad Idea, I fear. Sharing the same frontend is a recipe for bad
performance, lockups, bloat and corruption.

Not all end users have MS Access, so I am using the Packaging Wizard to
distribute the runtime version.

My questions:

1. Is there a way to distribute the runtime version only? So far, from what
I can see, it looks like you have to package an Access DB file with it. I
would like to be able to distribute the runtime "engine" alone, and then have
people follow a shortcut to the network file.

Once you have installed the runtime version of msaccess.exe (which the pacakge
does), then it can run any .mdb or .mde file. You just need to distribute the
frontend database, not reinstall the runtime.

2. If I have to package a file with it, is there any way I can get the
package to point to the HR Front End.mdb on the network? So far, from what I
can see, it looks like the packaging wizard installs a file to the user's PC.
Likewise for the security file, Security.mdw --- I want the users to always
be referencing the copy on the network.

Ummm... so do. Again, you're NOT required to rerun the Runtime install.

Hopefully it is clear what I am trying to do --- or, if this is not the most
elegant solution, can someone offer an alternative?

See Tony's updater:

http://www.granite.ab.ca/access/autofe.htm

or post back, there are ways to do this so that it's both effective and
painless for the user.