Runtime Package Updating

[Guest]

I created and distributed a runtime package. Now when I need make a change to
the formats or layouts of the forms in the package, I must rerieve all the
packages I distributed and make the changes to each one because the data in
each of the distributed package databases is constantly changing. Is there a
way I can distribute an update package that does not affect the data in the
databases?

 

[Guest]

Yes. You need to split the database into a front end (program) and backend
(data). Keep temporary files in the front end.

You can easily find out how to do it and what it means. You need to know
about linked files as well.

Try it on a test database with one file.

 

[Tony Toews [MVP]]

Yes. You need to split the database into a front end (program) and backend
(data). Keep temporary files in the front end.

You can easily find out how to do it and what it means. You need to know
about linked files as well.

You want to split the MDB into a Front End MDB containing the queries,
forms, reports, macros and modules with just the tables and
relationships in the Back End MDB. The FE is copied to each network
users computer. The FE MDB is linked to the tables in the back end
MDB which resides on a server. You make updates to the FE MDB and
distribute them to the users, likely as an MDE.

See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp/ for more info. See the
Auto FE Updater downloads page
http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless.. The utility also supports Terminal Server/Citrix quite
nicely.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Pieter Wijnen]

I Assume you mean temporary tables (Imports etc)
Even better is to have a seperate local BE for these (I usually create &
link to it on the fly - or use "direct" queries)

Pieter

 

[Guest]

I Assume you mean temporary tables (Imports etc)
Even better is to have a seperate local BE for these (I usually create &
link to it on the fly - or use "direct" queries)

Pieter

 

[Guest]

I Assume you mean temporary tables (Imports etc)
Even better is to have a seperate local BE for these (I usually create &
link to it on the fly - or use "direct" queries)

Pieter




Sorry everyone,

I assumed that the package needed to be splt, but this is an Access 2007
ACCDB.
How is this splitting accomplished retroactively?