I have a database created in Access 97 which I use a VB front end to access. I am using the ADOX object with the connection string as jet 3.51. I continuously get the error that the provider does not support the operation I am trying to do.
According to the Microsoft knowledge base, this is because I have to use the jet 4 engine by recreating my users in access 2000.
This is no good because my program opens an instance of access for certain tasks.
Is there another way round this. Can I use the ADOX object with version 3.51 of the jet engine??
Mega.
"If at first you don't succeed, then skydiving is not for you"
you dont CONVERT anything
you just use the Jet Engine 4.0 files
in your project
go to
project>references>select ADO 2.5 (2.6) if you have it
then use a jet engine string to opent he connection
Ok, update.
I have installed the jet 4 files (Service pack 5). I have made sure that all the references are okay in the code.
And yet....... I still get the error.
Someone is going to have to tell me how to resolve this step by step.
I searched the MS knowledge base and it suggests recreating the user MDW file in Access2000. that's ok except I dont have 2000. Another article states that this a bug..
How dam hard is it to find a article that provides any usefull information.
Please help....
Mega.
"If at first you don't succeed, then skydiving is not for you"
I have checked I am using the right reference (DDL & Security, ADO 2.6 etc...)
And I still get the same message
"Object or provider is not capable or performing requested operation"
I have opened the access database and also added these references to some of the modules I am using to see if that made any difference..
Any more suggestion, This was so easy in DAO...
Incidentally, I am using a database called "Asset.mdb" and a workgroup security file called "Asset.mdw". They are both on a network drive and my connection string looks like this.
Set cat = New ADOX.Catalog
cat.ActiveConnection = "Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=" & App.Path & "\Asset.mdb;user id = " & User & ";" & _
"password=" & Password & ";" & _
"jet oledb:system database=" & App.Path & "\Asset.mdw"
This looks right to me.. yes?
Mega.
Last edited by Mega_Man; Jun 26th, 2001 at 09:52 AM.
"If at first you don't succeed, then skydiving is not for you"
I have placed the connection string two posts above.
I also tried creating a brand new database and used the example of ADOX from the MSDN. and guess what?....... Yes, I still get the same error
I appreciate the help all you guys are giving but does any one have a sample code that they know defenitely works that they could attach to a post and also tell me exactly what references you have included in your project.
I would be most grateful, I am 100% certain that the problem lies with installed / not installed components but I could make sure for certain if I had working code.
Alternatively or in addition, I am yet again open to suggestions.
Thanks again.
Mega.
"If at first you don't succeed, then skydiving is not for you"
I am using microsoft activex data objects 2.6
and ADO etx 2.6 for ddl and security.
I tried using the code that you suggested and I still get the same error.
I also tried removing the references and re-adding them using the 2.1 as you suggest and I still get the same message.
Mega.
"If at first you don't succeed, then skydiving is not for you"
VB 6 Enterprise Edition SP4
ADO, SQL 7/2000, ASP and some JavaScript
>> Life goes on, but for how long? <<
If you can smile when things go wrong, you have someone in mind to blame
Weird, its hard to try and fix an error for someone, when I don't get it
I've attached a text file that may provide the reason why you are getting this error, it come from TechNet
Thanks in advance for any help provided.
VB 6 Enterprise Edition SP4
ADO, SQL 7/2000, ASP and some JavaScript
>> Life goes on, but for how long? <<
If you can smile when things go wrong, you have someone in mind to blame
The article you sent would seem to suggest that the error is commonplace when using the jet provider.
Unfortunately, it does not provide a resolution to the problem.
Thanks anyway.
Mega.
"If at first you don't succeed, then skydiving is not for you"
Ok, I decided to try something else,
I managed to get a hold of Office 2000 and I created a workgroup with some security and the same name.
The connection string and ADOX objects worked this time.
Problem is that I cannot use a Access 2000 MDW file with a Access 97 MDB file and the users who I am writing this for all have access 97.. So, there's a little useless update for you.
Mega.
"If at first you don't succeed, then skydiving is not for you"
I got the same problems when trying this in my last project. Only problem is beacuse the company I'm at is very strict with software on the system, I can't upgrade from MDAC 2.1 or SP3.
So I got round the problem by adding in the DAO library and using DAO just for the security bits, where I wanted to check users and groups etc.
VB6 sp5, SQL Server 2000, C#
There are no stupid questions. Only stupid people.
Yes, unfortunately, it looks as though I am going to have to do the same.
btw, what sort of company do you work for. If you are designing software, surely they should have the most up to date available.
Don't they know that service packs are released for a reason?
Mega.
"If at first you don't succeed, then skydiving is not for you"
I work for one2one (mobile phones) but all of the network is handled by ComputerAid, so designing software is a nightmare because I do not have the rights to install stuff on other peoples machines. Installing the exe and such files is ok, but because I have insufficent rights I can't overwrite any DLL's, so to get any software out I have to go through wads of red tape.
ComputerAid also only allow certain versions of things on the network that they have tested thoroughly ie MDAC 2.1 etc.
I actually now have 2.5 on my machine, but if they new that they would not support my machine if it fell over!
It is very restrictive in large companies where the IT is outsourced.
VB6 sp5, SQL Server 2000, C#
There are no stupid questions. Only stupid people.
Ahh, I see where you're coming from.
I also work for a large company but as we are in charge of all the I.T. here, I pretty much get to install what I want hehe.
Mega.
"If at first you don't succeed, then skydiving is not for you"