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