Does ADP not support SQL Server connectivity when not on default port?

  • Thread starter Thread starter po or
  • Start date Start date
P

po or

It looks to me like Microsoft Access (as I create a new ADP and fill
in connection information) is ignoring the client alias, and just
going out and connecting on the default SQL Server port (1433), which
of course fails.

I've not found any documentation saying ADPs ignore the client
aliases, but I can see it trying to connect on the wrong port.

Anyone have any info/pointers?
 
(e-mail address removed) (po or) wrote in
It looks to me like Microsoft Access (as I create a new ADP and fill
in connection information) is ignoring the client alias, and just
going out and connecting on the default SQL Server port (1433), which
of course fails.

I've not found any documentation saying ADPs ignore the client
aliases, but I can see it trying to connect on the wrong port.

Anyone have any info/pointers?
Click to expand...

I connect regularly through other ports using
,portnumber
after the regular address.

It's possible that you may have to use the ALL tab to set the Network Library
to DBMSCCON.
 
Lyle Fairfield said:
(e-mail address removed) (po or) wrote in


I connect regularly through other ports using
,portnumber
after the regular address.

It's possible that you may have to use the ALL tab to set the Network Library
to DBMSCCON.
Click to expand...


By default its set to DBMSSOCN (which I think you meant).

Further experimentation suggests the problem may be MDAC 9
(which is maybe a beta after all), but I'm not ready at
the moment to rollback to MDAC 2.8 just for this problem.
 
Back
Top