Re: problem connecting to ADO programmatically

Chris.Cheney wrote:

I suspect that when the original ConnectString was set, it had the
side- effect of setting other values in the component. If you then
change the ConnectString in a manner incompatible with those other
values, it causes errors. It can happen at design time too.

You may be right.

BTW what were the original ConnectString values?

Here is what I have in the component, as set by the wizard. This works
fine:

Provider=Microsoft.Jet.OLEDB.4.0;Password="";User ID=Admin;Data
Source=I:\Development\CAP\CapWatch\CAPWATCH 24 MAY 07.MDB;Mode=Share
Deny None;Extended Properties="";Jet OLEDB:System database="";Jet
OLEDB:Registry Path="";Jet OLEDB:Database Password="";Jet OLEDB:Engine
Type=4;Jet OLEDB:Database Locking Mode=0;Jet OLEDB:Global Partial Bulk
Ops=2;Jet OLEDB:Global Bulk Transactions=1;Jet OLEDB:New Database
Password="";Jet OLEDB:Create System Database=False;Jet OLEDB:Encrypt
Database=False;Jet OLEDB:Don't Copy Locale on Compact=False;Jet
OLEDB:Compact Without Replica Repair=False;Jet OLEDB:SFP=False

--

Bill
.