Yes, I've tried using the ADO data control (right-clicking on it and selecting properties), I've tried using the dataenvironment and configuring the connection... No matter what I try, it won't connect using Jet 4.0. If I set up a DSN and use the connection string "Provider=MSDASQL.1;Persist Security Info=False;Data Source=ContactsDSN;PWD=mypassword", it works fine. I really don't want to use ODBC, I want to use Jet. The connection string I've been trying that hasn't been working is "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=D:\Inetpub\databases\Contact.mdb;Persist Security Info=False;PWD=mypassword"

>>I've tried calling:
>> adoConnection.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\libtax 1999\libtax 1999.mdb;Persist Security Info=False;pwd=blah"
>>
>>and I've tried:
>> adoConnection.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\libtax 1999\libtax 1999.mdb;Persist Security Info=False;",,"blah".
>>
>>The first gives me a "Cannot find installable ISAM" message, the second gives me a "Your application cannot be started. The workgroup information file is missing or opened exclusively by another user."
>>
>>If I remove the password from the database, I can open it with no problem. This is an Access 2000 database and I'm using VB 6.0 with ADO 2.0.
>
>Have you tried the DataEnvironment? Not to use it. Only to build your connection string!