[AccessD] Re: Calling objects

Robert, 

(FYI The apps users are not all on the same Network.) 

I assume that method would work fine with mde's?

Ryan







"Robert L. Stewart" <rl_stewart at highstream.net>
Sent by: accessd-bounces at databaseadvisors.com
12/02/2004 13:16
Please respond to Access Developers discussion and problem solving 

 
        To:     rsmethurst at uk.ey.com
        cc:     accessd at databaseadvisors.com
        Subject:        [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


_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



 

  
This e-mail and any attachment are confidential and contain proprietary information, some or all of which may be legally privileged.  It is intended solely for the use of the individual or entity to which it is addressed.  If you are not the intended recipient, please notify the author immediately by telephone or by replying to this e-mail, and then delete all copies of the e-mail on your system.  If you are not the intended recipient, you must not use, disclose, distribute, copy, print or rely on this e-mail.

Whilst we have taken reasonable precautions to ensure that this e-mail and any attachment has been checked for viruses, we cannot guarantee that they are virus free and we cannot accept liability for any damage sustained as a result of software viruses.  We would advise that you carry out your own virus checks, especially before opening an attachment.

The UK firm Ernst & Young LLP is a limited liability partnership registered in England and Wales with registered number OC300001 and is a member practice of Ernst & Young Global.  A list of members? names is available for inspection at 1 More London Place, London, SE1 2AF, the firm?s principal place of business and its registered office.