I would try to remove WSID from the connection string to see if an ODBC driver may use current workstation name.
Or you can use DBSETPROP() function to modify connection string

DBSETPROP("ConnectionName", "CONNECTION", ConnectString, "...")

>
>I've used this code before for other purposes so I'm familar with this. However, use a lot of remote views and create them via the view designer and both the view and connection string are stored via the DBC (and I think the connection string is encrypted or compiled in some way) so I was hoping there was some trick on how to set up the ODBC connection string so that it would automatically pull the WSID. If there is not, is it possible to hack the connection string that is stored in the DBC?
>
>Thanks,
>Robert
>
>>You can use SYS(0) to get computer name and insert it into the connection string
>
>>I know how to create an ODBC connection string and include a fixed WSID reference in the string but I want the WSID to be picked up automatically at runtime from the computer that the program is being run on. The reason I need this is so I can look at the MS SQL Server Enterprise Manager and see any hung processes and be able to identify the workstation where the program is hung..