[AccessD] Re: Calling objects

Ryan,

I use a program called WinBatch.  I have the compiler version of it which 
allows me to create a stand alone executable for the installation.  I also 
use a program called WinRAR which is a compression program like 
WinZip.  The advantage is that I can create self-extracting files that can 
also run a specific program after extracting its contents to a specific 
directory.

So for your installation, I would simply use WinRAR to extract to a 
specific directory structure.  Personally, I use MSA_Prod\ProgName and 
place all of the production application in the same directory structure.  I 
would not need to use WinBatch in your case unless you were using a 
third-party active-X control or something like that.

By using an installation method like this, the images would be placed in 
the same directory on every machine and the linking would work properly and 
allow you to get away from embedding.  Another alternative, if everyone is 
on the same network, would be to put the images in a central location with 
the backend database and link to them there.  I would still keep the local 
structure for ease of maintenance.

Robert


At 10:31 AM 2/12/2004 +0000, you wrote:

>Robert,
>
>I am interested in the second part of your mail.  At the moment, this 
>database will not be shipped with an install program (as far as I am aware 
>it is just going to be emailed to strategic staff and they will then make 
>it downloadable).  Could you elaborate on how you ship Access databases 
>with an install program?  Sounds like a good suggestion.
>
>RyanS
>
>
>"Robert L. Stewart" <rl_stewart at highstream.net>
>
>11/02/2004 18:28
>
>         To:        accessd at databaseadvisors.com
>         cc:        rsmethurst at UK.EY.COM
>         Subject:        Re: Calling objects
>
>
>Ryan,
>
>You did ask for "best practice."  The best practice
>is not to do it.  Shipping it all over the place is
>not an excuse.  The install program could place them
>in the same directory as the Access FE then linking
>them is a no-brainer.  The most resource efficient
>way is not to do it.  Why you feel you have to have
>them is a matter for debate if you insist on the
>inefficient practice.
>
>Robert
>
>At 12:00 PM 2/11/2004 -0600, you wrote:
> >Date: Wed, 11 Feb 2004 17:11:14 +0000
> >From: rsmethurst at UK.EY.COM
> >Subject: Re: [AccessD] Calling objects
> >To: Access Developers discussion and problem solving
> >         <accessd at databaseadvisors.com>
> >Message-ID:
> >         <OF0DDD2076.113BC796-ON80256E37.005E4B7C-80256E37.005EA1DB at ey.net>
> >Content-Type: text/plain; charset="us-ascii"
> >
> >No,  the database is shipped all over the place, so they really need to be
> >embedded.
> >
> >In answer to Charlotte...they're icons for the main menu.  Why etc. is not
> >really what's up for debate at the moment, I'm just looking to make sure
> >it is done the most resource efficient way.
> >
> >Thanks
> >RyanS