Help with Import-overwrite reports

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

Guest

I have a database application that I need to update with a couple report
objects. I would like to write some code to take care of the matter. I
thought I would create a database with the corrected report objects and
export/import them to the database on the client machine. The machine only
has access runtime so I am not sure how to do this. Any help would be
greatly appreciated.

Thanks
 
You won't be able to do that if the client machines only have runtime. You
will have to redeploy your application to each user. There are a number of
ways to do this. One is the put the app in a shared folder and notify each
user to copy it from the shared folder to their computer. A slight
improvement on that is to provide each user a bat file that does it for them.
The absolute best is a front end updater application. Here is the basic
concept.

Each user will need in addtion to the app file, an Access front end update
application. Also, you will need to add a local table to the app that has
one field that contains the current app version. And a similar table in the
the back end database that contains the curren app version.

In the start up code of the app, you compare the b.e. version number to the
f.e. version number. If the f.e. version is not the current version, you
open the front end updater applcation and close the app.

The front end updater then moves the app file to a back up folder, and
copies the new version file to the user's computer from a shared folder.
When the copy is complete, the front end updater then starts the app and
closes itself.

All the user sees is a message (one you write in the front end updater) that
the app is being updated.
 
Thank you.

Klatuu said:
You won't be able to do that if the client machines only have runtime. You
will have to redeploy your application to each user. There are a number of
ways to do this. One is the put the app in a shared folder and notify each
user to copy it from the shared folder to their computer. A slight
improvement on that is to provide each user a bat file that does it for them.
The absolute best is a front end updater application. Here is the basic
concept.

Each user will need in addtion to the app file, an Access front end update
application. Also, you will need to add a local table to the app that has
one field that contains the current app version. And a similar table in the
the back end database that contains the curren app version.

In the start up code of the app, you compare the b.e. version number to the
f.e. version number. If the f.e. version is not the current version, you
open the front end updater applcation and close the app.

The front end updater then moves the app file to a back up folder, and
copies the new version file to the user's computer from a shared folder.
When the copy is complete, the front end updater then starts the app and
closes itself.

All the user sees is a message (one you write in the front end updater) that
the app is being updated.
 
Back
Top