Re: Avoid Hardcoding --Link tables in Access and Oracle

As long as it's hard-coded, there probably is no clean and easy way to swap. However, you could (in your test environment) modify the properties of the DSN (using the ODBC tool) to use the connect string for your test database. It's an easy way to swap for a testing situation, but any time you are swapping like this you've got to be careful you always know where you are. I would not give this kind of control to the end user.

If you really want/need a selection at run time, that would be an Access question, not an Oracle question. It's a matter of how Access can specify an ODBC DSN as a run time variable, not what database that DSN is pointing to.

In article <86q8gu$od4$1_at_nnrp1.deja.com>,   coakleyj_at_hotmail.com wrote:
> Hi all.
>
> I have inherited an application that uses MS ACCESS and Oracle 8.0.5,
> with MS ACCESS tables linked to Oracle tables.
>
> Now the DSN is hardcoded into the MS ACCESS Design, which makes it
> difficult/error prone in swopping between development, test and
> live databases.
>
> I have dome some preliminary work with linking
> tables in Access, and it always seems
> to require giving it either the DSN or the tnsnames entry at design
> time.
>
> Is there any way to aoid this, and force the user to specify the
> source to connect to (much like the default Oracle Forms login)
> and pass this detail at runtime?
>
> Thanks for the help
>
> Coakleyj
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Thu Jan 27 2000 - 15:09:08 CST