Best approach ...

  • Thread starter Thread starter Question Boy
  • Start date Start date
Q

Question Boy

Hello,

I have a db (already deployed at several locations). Since I deployed it I
have continued to develop new forms, report (with vba as well). i am looking
for a way to send an 'updater'. I was thinking a db with the new objects
that once launched using an autoexec macro would prompt the user to select
their db and then would proceed to import the objects.

I also have a concern because I locked down the VBA project with a password
to avoid people nosing around. So will the import bypass this or do I need
to be able to suplly it when performing the update? if so, how?

Thank you for your help,

QB
 
Question said:
I have a db (already deployed at several locations). Since I deployed it I
have continued to develop new forms, report (with vba as well). i am looking
for a way to send an 'updater'. I was thinking a db with the new objects
that once launched using an autoexec macro would prompt the user to select
their db and then would proceed to import the objects.

I also have a concern because I locked down the VBA project with a password
to avoid people nosing around. So will the import bypass this or do I need
to be able to suplly it when performing the update? if so, how?
Click to expand...


That would be nearly impossible to do correctly. Instead,
you should deliver/install a complete new copy of the front
end mdb file.

If you are not familiar with using front end and back end
mdb files, see:
http://www.granite.ab.ca/access/splitapp/index.htm

You will probably find this useful too:
http://www.granite.ab.ca/access/ufad.htm

and maybe this too:
http://www.granite.ab.ca/access/autofe.htm
 
Marshall.

Normally Isplit the db and that would be the approach I would take. Quick,
Clean and Easy!

Sadly, in this case, the db is not split (not even converted into an mde).
I am really needing to perform a live update of sorts to avoid data migration
headaches...

Any other suggestions (splitting the db is not an option in this case)?

QB
 
A long time ago I tried using TransferDatabase and
CopyObject, but ended up running myself in circles. Check
them out in VBA Help, maybe they will be sufficient in your
situation.
 
Back
Top