[Tom Tom]

If you really did intend to use SQL Server security because that's how your company or department has set up sccess to your SQL Server (perhaps because some clients are non-Microsoft), then you need to specify a user name and password in the connection string as shown here:

thisConnection.ConnectionString= _
"server = (local)\netsdk;" & _
"User id = sa;" & _
"password = x1y2z3"

The sa user name is the default system administrator account for SQL server. If a specific user has been set up, such as george or payroll, then specify that name. The password for sa is set when SQL Server is installed. If the user name you use has no password, you can omit the password clause entirely or specify an empty password, as follows:

password =;

However, a blank password is bad practice and should be avoided, even in a test enviroment

[willyoumind]

You've the point here, Tom.

I have never use the blank password, as it is totally insecure to me.
Plus, I can't afford to lose my accounts as well!