Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Avoid Hardcoding --Link tables in Access and Oracle

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

From: Mark Tomlinson <marktoml_at_hotmail.com>
Date: Thu, 27 Jan 2000 19:38:42 -0500
Message-ID: <s91p121a7q5128@corp.supernews.com>


There is an Access specific VBA API set for doing exactly that (linking at runtime). Been a long time since I looked at using it though...

<coakleyj_at_hotmail.com> wrote in message news:86q8gu$od4$1_at_nnrp1.deja.com...
> 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.
Received on Thu Jan 27 2000 - 18:38:42 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US