Import module

[abe6162]

Can I import a module after I complie the file as a MDE file.

Reason for the question:
I am going to set up a design master file on the network. I would like the users to import any new modules, forms introduced to the application.

Any help or suggestions would be appreciated

 

[PHV]

If you already have FE/BE architecture, simply update the whole BE, otherwise consider splitting your database.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244

 

[abe6162]

I am new to Access and I am setting up the archeiture.
I will have FE (mdb) and BE (mdb) on the Network. I would like to distrubte the FE as an MDE file to the user.

Reason for import module or forms:
When I make a change the FE (mdb file) on the network, like add a new form or add a new module, I would like the FE on the client side to get the change. I assumed I can use the DoCmd.TransferDatabase to transfer forms and modules, but it errored out.

 

[FancyPrairie]

I don't think you can do what you want with an MDE file. Even if it wasn't an MDE file, it could become pretty complicated.

You might want to consider copying the new version to the user's machine. This is how I do it and it really helps out with maintaining the database.

I created a library (just another database) and added a table. The table contains (at a minimum) 2 fields: name of the user's computer and a new version flag (mine also contains the name of the primary user of the pc, their phone number, office location, message flag, shutdown flag, etc.).

When the database is opened it checks to see if the computer is registered (i.e. does the computer name exist in the table). If not, then I popup a form and have the user register the computer (and fill in all of the info I need).

Now when I have a new version of the FE, I simply set the NewVersion flag for each pc I want to receive the new version. Most of the time all of the machines will need the new version. However, there may be times when you only want one user (or group of users to receive the new version (i.e. testers)). If the new version flag is set, I simply kick off a batch job, exit the db, copy the new version to the user's machine and restart the db.

I use the MessageFlag to broadcast a message to the user(s) (i.e. New Version available. Please exit db and rerun it). To do this I have an invisible form running on a timer (i.e. 1 minute). So every minute it checks to see if a message is to be displayed. If so, a form is popedup that displays the message. This invisible form also checks for the shutdown flag. If the shutdown flag is set, then the database immediately exists. I use the shutdown flag when I need everyone to get out of the db (maintenance or whatever).

Note that by including the name and phone number of the primary user, you can see who's logged onto your application and have their name and phone number displayed so you can contact them if need be. You also have a record of who's using your database and where it is installed.