[AccessD] Problem with Intial Reattach

Charlotte Foust wrote:
I have been doing the reattach with mdes for years.
On the initial install of the program a form pops up and asks the user 
to input the path to the backend. The program checks first to make sure 
the backend can be located in the path they have indicated then it  
establishes the links. It also records the path in a table, in the front 
end. Every time the user starts up the program it gets the path and 
checks to insure the backend still exists in the path (in case the IT 
people have moved it), if not it pops up a form indicating to the user 
that the backend cannot be found in the current path, and to enter in a 
new path (and it runs its' checks and reattaches to the new location). 
There is an option to ReAttach tables in the utilties on the Main Menu 
that will allow the user to link to a new location for the backend. On 
troublesome networks I usually get the user to attach to the backend on 
the local drive, then once we confirm the installation went fine and 
everything is working in the program, they can then attach to the 
backend on the network drive.  This way if we run into network problems 
we can inform the IT people the program is working fine, but we got 
network problems.

>Wait, are you using an mde front end?   I've had problems changing
>attached back ends when using an mde front end.  It seems to be
>something like changing references in an mde, not a simple task.  If it
>finds the correctly named file in the right location, it plays nicely.
>If not, it throws up because it needs to be recompiled with the new
>attachment location, and you can't do that in an mde AFAIK.
>
>Charlotte Foust 
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Tony Septav
>Sent: Monday, June 18, 2007 2:00 PM
>To: accessd at databaseadvisors.com
>Subject: [AccessD] Problem with Intial Reattach
>
>Hey Bryan
>I'd bet a week of Arthur's salary :) that that is the problem.
>
>Well Byran checked with the user and the dev machine, both have the most
>current Windows XP and Jet 4 SP updates.  I suggest you donate a week of
>Athur's salary  to the list.  Just kidding.
>
>Ran my test with 3 different versions of  the simple Access97  tester,
>everything worked fine.
>
>Then created 2 simple Access 2003 mde tester versions 1. App already
>linked to the backend folder,  simple main menu and form displaying a
>list of one the tables in the backend. Worked fine.
>2. Attach table form appears and asks the user to indicate the path to
>the backend. User types in the path and the error message appears
>"Active X component can't create object".  This app does not have any
>Active X controls.
>
>Still looking into a possible subtle SP difference but I think I have
>hit a "DLL from hell" problem.
>
>
>  
>