Auto install updates

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hey,
We have a rather large database now which is being used the other side of
the country. To make life easier we are trying to make an application in
access which will import updates to forms, queries and modules automatically
when the user inserts their update cd into their cd drive which we shall be
sending via post.

ive tried a macro but the problem is, importing updates to forms will put a
"1" on the end of the name since it already exists (i sense a
docmd.deleteobject coming on here) but im not quite 100% sure how to go about
it.
Any help greatly appreciated.

Thanks,
Ash.
 
Ashg657 said:
Hey,
We have a rather large database now which is being used the other
side of the country. To make life easier we are trying to make an
application in access which will import updates to forms, queries and
modules automatically when the user inserts their update cd into
their cd drive which we shall be sending via post.

ive tried a macro but the problem is, importing updates to forms will
put a "1" on the end of the name since it already exists (i sense a
docmd.deleteobject coming on here) but im not quite 100% sure how to
go about it.
Any help greatly appreciated.

Thanks,
Ash.
Click to expand...

Your app should be split into two files. One with just tables and one with
everything else. The second file has links to the tables in the first and is
the file that is then opened and used. This arrangement allows you to
distribute changes by simply replacing the entire "front end" file. Virtually
all serious Access development uses this setup.

It is relatively easy to change a monolithic file into a split application.
There is even a wizard that will do it for you.
 
thanks for your opinion Rick, however im afraid this is not possible. We
already just have a single database file setup in 12 different sites up and
down the country, they are accounting systems. Making this change would mean
a major revamp of all sites, simply not achievable anytime soon.

Its a good suggestion though any others are welcome for single database
formats.

Thanks again,
Ash.
 
Not having your application split into a front-end and back-end like Rick
suggests is a very bad decision.

The risk of database corruption increases significantly when you have
multiple users sharing the same database. Only your back-end database should
be on the server: each user should have his/her own copy of the front-end,
ideally on their hard drive. Tony Toews has a free utility that ensures that
each user always has the most up-to-date version of the front-end at
http://www.granite.ab.ca/access/autofe.htm

Realistically, it isn't that much work to split. For the time you're
spending trying to resolve your update problem, you could have a split
application!
 
There are no servers involved. The databases just sit on a single PC with a
single version at each site.
It is not my decision to make major changes to our existing system but will
bear your suggestions in mind and put them forward to my boss.

Thanks again,
Ash.
 
Back
Top