Updating Programs in Access

[Paul Richards]

I am developing a system for some clients. They currently have version 1
of the system and are building up the data om the databases. When I have
developed version 2 how can I install this on their PC without
overwriting the data they have accumulated?

What I need to do is update forms, queries, reports etc but leave the
base data unchanged.

Thanks

 

[Albert D.Kallal]

You should have split you database.

I explain in detail here why you do this

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

If you split the database, then I even offer a "web" update button in my
application. here is some screen shots that show this

http://www.kallal.ca/ridestutorial/upgrade.html

I simply execute a followhyper link to my web site..and they can then update
the software anytime they need to....

in your case, simply send them a new front end, and have it link to the
existing non-split back end (this means your existing application will
become the back end...and you simply send them a new front end without the
data....

 

[Paul Richards]

Albert: what if I haven't split the database?

 

[Albert D.Kallal]

Albert: what if I haven't split the database?

Simply split your copy...and then, I shall re-post what I suggested...

quote ---

end quote ---

 

[Paul Richards]

What’s wrong with using replication to create a Design Master?

 

[George Nicholson]

Replication is really only intended for synchronizing *data* changes. It
doesn't handle significant form & report changes all that well. (It isn't
all that crazy about heavy changes to table structure either, if I remember
correctly, but that may have been just my experience).

In any case, you would still have a similar issue: your design master would
need to have been set up *before* it was distributed and data added by the
client.


HTH,

 

[Albert D.Kallal]

What’s wrong with using replication to create a Design Master?

because the client already have a operational application deployed on site.
The user is looking for a way to send them a new updated appcation, but not
touch the data part. So, simply creating a new front end that will link to
the existing data file makes sense. The fact that the original appcation is
not split really don't matter, since you can send a new front end that will
link to their existing data file.

With replication, all kinds of new setup, and data files will have to be
created, and THEN placed on the clients computer, and further, to set that
up, either you have to travel to the clients location, or have the client
send you THEIR data while you setup replication. And, further, replication
assumes that you have some type of connection, which one may, or may not
have. Really, quite a complex process as compared to simply emailing a
client a new zipped mde file....

Further, as noted, replication is for replication of data, and trying to use
it for replication of software updates to an application is a disaster at
best, and at worst will not work for a mde file.....

 

[Paul Richards]

So the best bet is to create an Access project with separate data and
application parts as you suggest?

 

[DrZilboorg via AccessMonster.com]

Best bet???

I'm just getting my arms around this stuff, but from what was presented, it's
the only bet if you aren't in the disaster recovery business.

I'll be splitting the DB I'm working on, and I don't plan on distributing it
anywhere. But I might be networking the business that I'm building it for at
some point in the future, and it makes sense to do it.

 

[John Nurick]

Doesn't have to be an ADP if that's what you had in mind; but yes, split
the data store and the front end.