I've created a database in Access 97, which sits on a server, and written a front-end to connect to it using "Microsoft.jet.OLEDB.3.51". Question is when this is installed on machines without Access or with other versions it fails to recognise the provider, am I stuck with this?
Thanks in anticipation
If the machine has never had Access on it (or has a later version) then you won't have the Jet 3.5 provider. There are a few work arounds noted in MSDN.
Although it is a bit late now your best bet would be to use ADO and ship MDAC with you DB front end. Then it will work for everyone (not to mention the fact that you don't have to work with DAO).
Thanks for the reply,
Sorry I wasn't very clear in my original post, I am using ADO and do ship MDAC2.5 and DCOM95 with the install but still no joy, any ideas
Thanks again Phil
Personally I don't know what I'm talking about. Trying to have a discussion about providers and relate it to DAO!?! You'll have to forgive me.
Anyway, I found this snippet from a document written by some guy at MS:
I use the Jet 4.0 driver over the 3.51 for a few reasons. One reason is that the Jet 4.0 provider is included with Microsoft Data Access Components. This is a more current implementation of the Jet engine, so it has more features. Using the 4.0 provider will save you from having to make changes to your code when you move to Access 2000.
It appears that number 4 is the way to go.