Re-linking to different tables

[Gordon]

I have a database split between a front (FE) and back end (BE). I do
a lot of form design changes, aimed at importing and manipulating data
in the BE.

For developement purposes, I want to have a form with a button that I
can press to be able to programmatically switch the BE tables to a
different set - a development set.

Am I heading in the wrong direction here? Is there any standard code
that I can use to effectively unlink the currently attached tables and
re-connect the FE to a new set of tables?

Thanks for any help

Gordon

 

[Stuart McCall]

I have a database split between a front (FE) and back end (BE). I do
a lot of form design changes, aimed at importing and manipulating data
in the BE.

For developement purposes, I want to have a form with a button that I
can press to be able to programmatically switch the BE tables to a
different set - a development set.

Am I heading in the wrong direction here? Is there any standard code
that I can use to effectively unlink the currently attached tables and
re-connect the FE to a new set of tables?

Thanks for any help

Gordon

The simplest and easiest method is to swap the BE files as appropriate, then
open the FE. The tables will remain linked. However, if you make any changes
to one copy of the BE then the other copy will need the links for the
modified tables to be refreshed. For this use the Linked table manager.

 

[Stuart McCall]

I have a database split between a front (FE) and back end (BE). I do
a lot of form design changes, aimed at importing and manipulating data
in the BE.

For developement purposes, I want to have a form with a button that I
can press to be able to programmatically switch the BE tables to a
different set - a development set.

Am I heading in the wrong direction here? Is there any standard code
that I can use to effectively unlink the currently attached tables and
re-connect the FE to a new set of tables?

Thanks for any help

Gordon

The simplest and easiest method is to swap the BE files as appropriate, then
open the FE. The tables will remain linked. However, if you make any changes
to one copy of the BE then the other copy will need the links for the
modified tables to be refreshed. For this use the Linked table manager.

 

[Douglas J. Steele]

Take a look at http://www.mvps.org/access/tables/tbl0009.htm at "The Access
Web". It doesn't do exactly what you're looking for (it prompts the user to
search for the back end), but you should be able to modify it for your
purposes.

 

[Gordon]

Take a look athttp://www.mvps.org/access/tables/tbl0009.htmat "The Access
Web". It doesn't do exactly what you're looking for (it prompts the user to
search for the back end), but you should be able to modify it for your
purposes.

--
Doug Steele, Microsoft Access MVPhttp://I.Am/DougSteele
(no private e-mails, please)










- Show quoted text -

Thanks both for coming back to me, but Doug......you're wrong. The
code you pointd me to does EXACTLY what I want. I want to be prompted
to point to the new datastore location.

Thanks again.

Gordon

 

[Douglas J. Steele]

Glad it was what you wanted.

I've always given the user a choice of environment in which to work (i.e.
"Development", "Test", "Production"), and decided to which back-end that
equated, rather than allowing them pick the actual file location. (I
typically have an INI file associated with the application, with the mapping
from environment to file included as part of the INI file)

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

Take a look athttp://www.mvps.org/access/tables/tbl0009.htmat "The Access
Web". It doesn't do exactly what you're looking for (it prompts the user
to
search for the back end), but you should be able to modify it for your
purposes.
- Show quoted text -

Thanks both for coming back to me, but Doug......you're wrong. The
code you pointd me to does EXACTLY what I want. I want to be prompted
to point to the new datastore location.

Thanks again.

Gordon