sharing Modules

[Peter Kannowade]

Hello,

using a database with several Access97-Frontends I would like to share
components between the frontends.

I would like to put VBA-code into some Module.mdb and link them to the
frontends.

We have a developent version and a production version of the frontends
and so we would also have developement and production versions of the
modules.

How can I easily make shure that the development frontend uses the
developement modules and that the production frontend uses the
production modules?

How can I easily update the production version while some 20 continue
their work?
Current solution: start.bat copys the production frontend and executes
the copy thus nobody stays connected to the master frontend which can be
updated at any time - if a user starts after the update he gets the new
version.

Thank you for your Ideas

Peter

 

[Chris]

You can include a reference to the modules.mdb file, then reference it as
Module.MacroName.

But, you might want to create .dll's for this too. That's what .dll's are
for.

 

[Marshall Barton]

using a database with several Access97-Frontends I would like to share
components between the frontends.

I would like to put VBA-code into some Module.mdb and link them to the
frontends.

We have a developent version and a production version of the frontends
and so we would also have developement and production versions of the
modules.

How can I easily make shure that the development frontend uses the
developement modules and that the production frontend uses the
production modules?

Each fe db needs a Reference to your modules db. Since a
broken reference can prevent code from running, you'll be
best served by manually resetting the reference just before
making a development fe into a production fe.

How can I easily update the production version while some 20 continue
their work?
Current solution: start.bat copys the production frontend and executes
the copy thus nobody stays connected to the master frontend which can be
updated at any time - if a user starts after the update he gets the new
version.

Your batch script is a good approach. Download Tony Toews'
Auto FE Updater at:
http://www.granite.ab.ca/accsmstr.htm
for a pretty comprehensive approach to updating production
versions.

 

[Peter Kannowade]

We don't own the complete vb. For DLLs we use C. I'm looking for a way
to get developers who don't know the c-language working together.

Thank you for the hint with the references. But what if I forget do
change the reference when I release a new production version? I would
have the users working on the develoment modules.mdb.

Peter

 

[Peter Kannowade]

thank you for your help - however I would like to make sure that nobody
forgets to change the reference when releasing a new production
frontend. I'll have a look to the link too to improve the starter.

Peter