I'm having a complicated linking problem. Before I get into the particulars,
I'd like to know how Access links to the back-end file at startup, AFTER I've
distributed my application to the client.
Here's the issue. While I'm working on my app, I'm linked to the backend on
my computer. When I distribute the app, the backend file is obviously in a
different location (on the client server).
But the first time my app is started up at the client location, the
connection strings for the backend will still be to my development computer
and these strings are obviously invalid.
Now I have a custom linking routine and use a launcher. The launcher passes
to my app via Command, the correct location of the backend files. This has
worked flawlessly over the past 6 months, but a recent update to the client
failed to work and generated a linking error. But, I'm having trouble
replicating the problem.
So, for now, I would just like to know what Access does when it encounters
the situation I mentioned. Is an error generated only if code or some action
attempts to extract data from a table link that is not valid. In other words,
Access will allow the invalid connection strings on startup and an error is
only generated when some action is taken to actually view or select data from
the linked table. I should mention that I use RWOP queries as well, so I
guess I'm wondering why there isn't an error generated at startup when the
RWOP query selects data from the linked table. I guess this must mean that
it doesn't actually select until an action of some type is taken (i.e. the
user opens the RWOP query or code tries to perform an action on the query).
Understanding how this works, I think will help me in solving my problem.
Thanks.
--
Message posted via http://www.accessmonster.com
I'd like to know how Access links to the back-end file at startup, AFTER I've
distributed my application to the client.
Here's the issue. While I'm working on my app, I'm linked to the backend on
my computer. When I distribute the app, the backend file is obviously in a
different location (on the client server).
But the first time my app is started up at the client location, the
connection strings for the backend will still be to my development computer
and these strings are obviously invalid.
Now I have a custom linking routine and use a launcher. The launcher passes
to my app via Command, the correct location of the backend files. This has
worked flawlessly over the past 6 months, but a recent update to the client
failed to work and generated a linking error. But, I'm having trouble
replicating the problem.
So, for now, I would just like to know what Access does when it encounters
the situation I mentioned. Is an error generated only if code or some action
attempts to extract data from a table link that is not valid. In other words,
Access will allow the invalid connection strings on startup and an error is
only generated when some action is taken to actually view or select data from
the linked table. I should mention that I use RWOP queries as well, so I
guess I'm wondering why there isn't an error generated at startup when the
RWOP query selects data from the linked table. I guess this must mean that
it doesn't actually select until an action of some type is taken (i.e. the
user opens the RWOP query or code tries to perform an action on the query).
Understanding how this works, I think will help me in solving my problem.
Thanks.
--
Message posted via http://www.accessmonster.com
Comment