Re: Refreshing Referenced Module
- From: "Axel" <realraven2000@xxxxxxxxxxx>
- Date: 31 May 2006 04:18:09 -0700
the front end is probably the best way, but hard to enforce as the app
runs in three plants. (3 Bosses and close to 50 users to convince) -
they are not used to tight version control although the original author
(he is one of the bosses) constantly potters with the frontend.
They might simply refuse to run it. So better if I could invoke this
app in Access.autorun and close down / restart (which is effecitvely
like bootstrapping). Of course I could take the lazy route and just
deny access + point to a batch file: "Your app is out of date, please
run RefreshDB!" - admittedly the cheapest way out.
thanks
Axel
wannall@xxxxxxxxxxxxx wrote:
Thereis no technique you can use to replace an in-use Access mdb.
If your people will be using them locally, you can copy the new bits down
before you open any of them. I still do this with VB (well, VB.NET now) as
a front-end to my access app. The little version checker/copier is so small
that the overhead is negligible, considering the version stay up to date
constantly, and it's capable of checking and copying only exactly what's
needed.
Not to mention that using a vb or vb.net app ahead of the access pieces
opens up all kinds of other possibilities about how you can respond to
command lines.
.
- References:
- Refreshing Referenced Module
- From: Axel
- Re: Refreshing Referenced Module
- From: wannall
- Refreshing Referenced Module
- Prev by Date: Code to add and verify existing data
- Next by Date: Make linked table have a relative path
- Previous by thread: Re: Refreshing Referenced Module
- Next by thread: Licensing / Packaging Excel components with an Access application?
- Index(es):
Relevant Pages
|