Updates and Distribution

  • Thread starter Thread starter David
  • Start date Start date
D

David

Hello,

I have developed an access program that is installed in
several locations. What is the best way to distribute
changes and updates?

I have split the database and the source at one point but
this slowed some parts of the database down over the
network to unacceptible performance.

If anyone has a working process for updates, I would
appreciate some advice.

Thanks
david
 
Splitting the database is pretty standard -
and makes it possible to swap out the front end without affecting the
data -
assuming there are no changes in data structure.
You might want to search the Google archives -
your problem of slow performance over the network gets regular coverage
in the newsgroups.

Failing that, you can build queries into your database which will transfer
data into your new mdb.
The problem there, of course, is that you can't just overwrite the old mdb
with the new one; you'll have to put it in another location, at least until
the transfer is complete.
I used to have some code that worked adequately to swap out entire forms
and reports in Access 97 - it developed some problems when we moved to
Access 2000, and it never really seemed worthwhile to go troubleshooting
(the need was diminishing at that point), but if you're sure that's the way
you need to go, holler back and I'll see what I can resurrect.

HTH
- Turtle
 
Hello MacDermott,

Thanks for your input, it is great help. I think I might
rewrite the whole thing using the .net IDE. I think I have
stretched Access to its limits in this application.

Have a great day,
David
 
..NET is the way of the future -
or so Microsoft would have it.
I've enjoyed working in it.

But don't underestimate Access -
it can do an awful lot!

= Turtle
 
Back
Top