Re: Linked Table Properties - using ODBC trying to rmv DATABASE NA

Tech-Archive recommends: Speed Up your PC by fixing your registry

Dear Tim,

I am asking about the MS access interface. It does not allow me to change
the connect parms after creating a link table. I do not understand why this
is so. In the earlier versions, I could do this.

The relink is executed by calling the refreshLink method. I have no
problems when in the past I just set the parms with "ODBC;DSN=ONYX" without
any passwords or users etc. This is what I am trying to get at. The current
2000-2003 versions puts in the other parms such as database= etc. I do not
think that it needs it internally, as the database should be extracted from
the DSN. The DSN setup also has the appropriate signon and password. It
does not make sense, if we need to set up all this info will it override the
current DSN settings on the computer?

This was working fine in the old versions where i had just ODBC and the DSN;
I tried resetting the connect string in the refreshLink method but it does
not reset the Link Table for some reason. Is there antoher method I have to
call first.









"Tim Ferguson" wrote:

> =?Utf-8?B?ZHBj?= <dpc@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> news:CDE5B5BE-DEB9-4338-A936-DDD8B119258B@xxxxxxxxxxxxx:
>
> >
> > However, when I move it to my staging machine, the database Onyx_Dev
> > is no longer there and it fails. In the past I could modify the
> > connect string such that it would only read:
> > ODBC;DSN=ONYX;UID=onyx1;TABLE=dbo.company
> >
> > Now in my application my old linked tables still work although they
> > have these old settings. However my new tables will not work and my
> > relink script fails. When I move the applcation from one region to
> > another.
> >
> >
>
> You don't give much detail of _how_ you are regenerating the link. The
> details of what has to go in the .Connect property of the Tabledef object
> are outlined in Access (DAO) help, and will be given more specifically in
> the provider's help file (for SQL Server, probably look in the Books On
> Line file).
>
> After resetting the .Connect property, remember to call the .RefreshLink
> method -- that is the one that actually goes out to find the data.
>
> You haven't put any password string in the Connect string you posted: I
> guess you are doing so in Real Life.
>
> HTH
>
>
> Tim F
>
>
.

Relevant Pages

  • Re: Question re MailMerge and VB.NET
    ... There is an ODBC API call to create a DSN which you should, in theory, call ... ' lpszDriver is a string containing the Driver name /exactly/ as it appears ... Private Const ODBC_CONFIG_DSN = 2 ... ' an example showing how to make a SQL Server DSN ...
    (microsoft.public.word.mailmerge.fields)
  • RE: Run-time error 3011 using Foxpro ODBC
    ... it is enough to just mention the DSN. ... -The constant acTable is ignored unless the database source type is MS ... Dim strConnect As String ... DoCmd.TransferDatabase acImport, "ODBC Database", strConnect,, ...
    (microsoft.public.data.odbc)
  • RE: Edit ODBC settings
    ... simply hard-coding the new DSN for each), but found that it was failing ... because my ProvideX ODBC connect string exceeds 255 characters when I use the ... T:\DBFolder to C:\Data\Apps\DBFolder so that it will work on the server. ... can I now edit the path in the ODBC-linked table to reflect the local path in ...
    (microsoft.public.access.queries)
  • Re: Word 2003 MailMerge with SQL Server 2000 problem
    ... Okay, I switched the way I was connecting, and started using a DSN ... If I could either create a DSN-less connection string for Mail Merge, ... Personally I wouldn't use the 1=1 workaround on the grounds that the query ... SQL Server does but I once did this with Oracle to get around some problem ...
    (microsoft.public.word.mailmerge.fields)