In a message dated 96-01-09 08:36:32 EST, you write:
 
>I have just switched over to W95 and its Winsock (previously
>using WRQ NS3000 connection Winsock) and I am now getting
>Server name errors.
>
>It would appear that it is something to do with the Server
>name entry in the ODBC setup. I've tried replacing this with
>my server's IP address but it still doesn't want to work.
>
>
 
OK,
I think I can help you here.  I have the same setup here whereby I access my
IMAGE/SQL database on my 3000 from my Windows 95-based PCs via the Windows
supplied TCP/IP stack and WINSOCK dll.  There is a simple quirk to enable
this however, make sure that you have the dll RNNSVT.DLL from WRQ somewhere
in your path. Be aware that Windows 95 default path is C:\Windows,
\Windows\command.
 
I have a very simple autoexec file:
 
set fultemp=c:\temp     /* this is required for HP Laserom */
path = c:\wrns,\dos,\word    /*wrns contains RNNSVT.DLL*/
set temp=:\temp
 
My config.sys is even simpler, it has nothing but REMs containing old
real-time drivers.
The PCs have modems, NIC cards, sound cards, CD-ROMs, graphics accelerators,
Enhanced IDE controllers, joysticks, laserjets and deskjets yet config.sys
and autoexec.bat have absolutely no references to any device.
 
Kind regards,
 
Denys. . .