B
bliss66
I'm trying to follow instructions in a third-party manual (Access 2002 VBA
Handbook by Novalis and Jones), regarding an ADO connection using this code
in the Immediate Window (I'm actually using Access 2003):
Set rst = New ADODB.Recordset
Set cnn = New ADODB.Connection
cnn.ConnectionString="Provider=Microsoft.Jet.OLEDB.4.0;DataSource=c:\VBAHand
book\Expenses.mdb;Jet OLEDB
atabase Password=expenses"
cnn.Open
After the fourth line, I get the following error message:
"Run-time error '-2147467259(80004005)
Could not find installable ISAM."
I located a kb article about editing Jet 4.0 registry entries but, as far as
I could tell, all of the entries contained valid paths.
I also saw some posts here suggesting the installation of MDAC 2.8 (which
apparently wasn't on my machine, only references up to 2.7 were installed)
but that hasn't made a difference.
I have also confirmed the DDL and Security type reference but it hasn't
changed anything.
The above file path in the string is correct. The only other thing I could
think of was that maybe a new security feature of Access 2003 was preventing
me from using this code. The client database is just the sample Northwind
database and the data source is just a database I created with the
wizard--I'm not aware that either are particularly restrictive.
Any other ideas? This computer runs a development edition of SQL Server
2000 SP3 but I wouldn't have thought that would make any difference since it
has nothing to do with the functionality of Access nor the connection
string.
Thanks for your help.
sb
Handbook by Novalis and Jones), regarding an ADO connection using this code
in the Immediate Window (I'm actually using Access 2003):
Set rst = New ADODB.Recordset
Set cnn = New ADODB.Connection
cnn.ConnectionString="Provider=Microsoft.Jet.OLEDB.4.0;DataSource=c:\VBAHand
book\Expenses.mdb;Jet OLEDB
atabase Password=expenses"cnn.Open
After the fourth line, I get the following error message:
"Run-time error '-2147467259(80004005)
Could not find installable ISAM."
I located a kb article about editing Jet 4.0 registry entries but, as far as
I could tell, all of the entries contained valid paths.
I also saw some posts here suggesting the installation of MDAC 2.8 (which
apparently wasn't on my machine, only references up to 2.7 were installed)
but that hasn't made a difference.
I have also confirmed the DDL and Security type reference but it hasn't
changed anything.
The above file path in the string is correct. The only other thing I could
think of was that maybe a new security feature of Access 2003 was preventing
me from using this code. The client database is just the sample Northwind
database and the data source is just a database I created with the
wizard--I'm not aware that either are particularly restrictive.
Any other ideas? This computer runs a development edition of SQL Server
2000 SP3 but I wouldn't have thought that would make any difference since it
has nothing to do with the functionality of Access nor the connection
string.
Thanks for your help.
sb