Bob,

What OS do you have? If NT then check how SQL Server DSN configered in ODBC Data Source. There are two options for "How should SQL Server verify the authenticity". It should be "With Windows NT authentication using the network login ID". Also try to test connection when in dialog.

In the program you actually can obtain DSN-less connection in DBC using 'create connection' with connstring option.

Anyway in your case [.null. user] looks suspicious. It may indicate that network can not recognize the PC name, or somehow the SQL Administrator did not give the trusted connection to this PC.

Yuri

>>>>>>>>>>>>>>>>>>>>>>>> your message below <<<<<<<<

I have a connection in my DBC that I populate with the DSN name then I open a view that uses that connection. If this is the first time opening a remote view a connection needs to be made.

The DSN is set up to use SQL Server login, but I get an error message that the .null. user couldn't be logged in on a trusted connection, then if I press ok the SQL server login comes up.

Why is it trying to connect trusted when the DSN is set up for SQL sercurity? Is there anyway to suppress that error so it just provides the SQL login?

Also, the login screen puts the cursor in the password field and the username is empty... why isn't the cursor in the username field?

Thanks,
BOb