"David Shorthouse" wrote:
> John,
>
> Thanks for the pointer to think about doing this more efficiently. I
> just found this:
>
http://support.microsoft.com/default.aspx?scid=kb;en-us;892490 and it
> appears to work great. However, it looks geared to Access 2002/2003. Does it
> work with Access 2000?
>
> Dave
>
> --
> ______________________________
> Remove "_SPAM" to reply directly.
> "John Bell" <jbellnewsposts@hotmail.com> wrote in message
> news:2B272D5D-E863-4029-BB86-40159054BEDD@microsoft.com...
> > Hi
> >
> > This seems to be under:
> >
> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo
> >
> > but you are probably better off using a DSN-Less connection.
> >
> > John
> >
> > "David Shorthouse" wrote:
> >
> >> I thought I would also add that I have the server address in my vbscript
> >> as
> >> "server,port" the client for which I am testing this odbc DSN connection
> >> receives an error 11 when an attempt is made to use this connection.
> >>
> >> Dave
> >>
> >> --
> >> ______________________________
> >> Remove "_SPAM" to reply directly.
> >> "David Shorthouse" <davidshorthouse@shaw_SPAM.ca> wrote in message
> >> news:ufyve62hFHA.1480@TK2MSFTNGP10.phx.gbl...
> >> > Hello folks,
> >> >
> >> > I'm using a port other than 1433 for my SQL Server 2000 database and
> >> > am
> >> > trying to write a vbscript to automate client's ODBC DSN creation. Is
> >> > it
> >> > possible to specify the port used in such a script? I have "Database",
> >> > "Descriptions", "Driver", and "Server" additions to the client's
> >> > registry
> >> > via the script, but what about specifying the port? Can this be done
> >> > via
> >> > WshShell.RegWrite?
> >> >
> >> > Thanks for any assistance,
> >> >
> >> > Dave
> >> >
> >> > --
> >> > ______________________________
> >> > Remove "_SPAM" to reply directly.
> >> >
> >>
> >>
> >>
>
>