[AccessD] Deployment Woes

Hi Mark

I can't see how to circumvent creating a new shortcut which will (run
a new batch file which will) launch a local copy of the FE.

Sometimes you have to bite the bullet to obtain a reliable setup and
- as you don't need to install Access - you can use a free installer
like Inno Setup to achieve this:

  http://www.jrsoftware.org/

It may take a little extra effort, but you won't regret this.

/gustav


> Brett, Jim, Gustav,

> This is the first application that I've really had to tweak to be
> "enterprise" ready.  Most all of my previous apps were "low usage"...more
> office automation or strictly robust reporting tools...no real concurrency
> issues.  This application has grown to include multiple data entry persons
> as well as simultaneous users.  I'm open for any suggestions regarding best
> practices.

> So, to combine the suggestions thus far, here is the current plan...

> 1.  Split the db.
> 2.  Move FE material to new FE db.
> 3.  Create a version table in new FE db.
> 4.  Create a version table in the launcher app db.

> Utilize existing db as a launcher app that:
> 5.  Logs in user.
> 6.  Verifies current version.
> 7.  Calls a .bat file which, if needed:
> 8.  Creates the new directory structure for the local FE.
> 9.  Copies down the new FE and supporting files.
> 10. Launches the new FE.

> Did I miss anything?  Should I try something else?