PMFJI - and sorry if I missed something - but it sounds like you need to be using SQLStringconenct - I use this and connect to SQL server with no database, no DNS, no nothing - it works great.

Sorry if I missed a point somewhere in here - I'm skimming messages quickly.

KEn

>>This needs to be done without the DNS entry.
>
>I'm assuming that you can get the connection to work when you DO have DNS...
>
>If you have an NT server with a few extra CPU cycles, you could enable WINS on it. Then you could enable the application's workstation with WINS in the TCP/IP protocol config. (WINS acts like a hybrid of DNS and DHCP, where the client machine tells the WINS server its name/IP address, and then asks the server for an address whenever it can't find a name in the local network- eventually all your machines should be able to talk to each other via TCP/IP.) Be aware that this will make microsoft file sharing on TCP/IP accessible over the internet.
>
>You could also look into the HOSTS file. This is a listing of name/address pairs stored on the workstation. It's preferred because it's a nightmare to administrate more than 3 machines, but it might be worth investigating for your application. (I don't know much about it, but you could search an appropriate conference for more info on the HOSTS file)
>
>HTH