06-28-2002, 02:28 PM
I have this application that uses ADO and works fine on ever other Windows OS but I get a 3709 error when I try to run it on XP.
I used to get that error on some Win 98 machines but when I updated the MDAC2.7 it ran just fine.
My Provider in my connectionstring in the application is "Provider=Microsoft.Jet.OLEDB.4.0...ect"
PLEASE HELP, This is giving me a headache!!! :(
06-28-2002, 02:35 PM
Try installing MDAC on the Windows XP machine.
06-28-2002, 02:40 PM
I did install the MDAC and no luck.
06-28-2002, 02:47 PM
Which version of MDAC?
06-28-2002, 02:51 PM
I think that is the newest.
06-28-2002, 03:42 PM
2.7 does not ship with Jet, you need 2.5
06-28-2002, 03:56 PM
I tried loading the latest JET service pack, JET40SP6_WXP.exe.
Wouldn't that have the same result?
06-28-2002, 04:09 PM
No, a service pack does not contain the core components.
06-28-2002, 04:11 PM
Thanks Robby I will give it a shot.
06-28-2002, 04:58 PM
That particular service pack is for Office XP. It won't necessarily
have the Jet data access components that were left out of mdac
2.6 and 2.7. In addition, since XP ships with 2.7 installed, you
won't be able to install 2.5 on top of it. You need to get the true
jet data access components update from http://www.microsoft.com/data/download.htm#Jet4SP3info
Look for Jet40sp3_comp.exe
07-03-2002, 10:06 AM
I have tried all of the suggestions and still the same results, 3709 error. Maybe I am barking up the wrong tree. Keep in mind that it works great on 95/98/Me/2K, just not XP.
What else could be causing this error? And then would be the solution?
A frustrated developer!
07-03-2002, 10:28 AM
At what point do you get the error message? (during connection, append, etc..)
Which version of Access?
07-03-2002, 10:33 AM
Well heres the thing...
We don't have an XP machine at the office so I have to do my testing on a machine off site. That was actually what I was going to do next. Load VB on an XP machine and then step through it to see where is bombs out.
The best I can tell is that it craps out at the connection but I will know more after the long weekend.
07-03-2002, 10:49 AM
keep us posted...
btw, Which version of Access are you using?
07-03-2002, 11:38 AM
My databases are Access 2000.
What I am trying now is adding in an user id and password in the connectionstring.
We will see.
07-10-2002, 02:23 PM
OK, so I loaded VB 6 on an xp machine and tried to run my app. It doesn't seem to crap out at the connection but at ever...
command. Aren't these commands in libaries that come loaded with the OS? Why doesn't XP have them loaded.
I get an "Can't find project or libary".
07-10-2002, 03:19 PM
Are you getting this error while in VB IDE?
Open references, are there any marked as "Missing" ?
Actually can you list all the references which are checked.
07-10-2002, 03:55 PM
Well, yes it is happening on the IDE but I think I was jumping the gun a little bit. Although that is a problem that will need to be solved the connection actually craps out at the ...
Set cnnUPC = New ADODB.Connection
statement. cnnUPC is Dimmed as ...
Public cnnUPC As ADODB.Connection
I get a runtime error of 429 "ActiveX component can't create object" at the Set cnnUPC statement.
I had a On Error Resume Next statement that was sqewing my thoughts a little. I am not at the XP machine anymore and it is off site so I will check the references next time I go.
07-11-2002, 11:24 AM
There is a new service pack just for Access/Jet and it has unique
versions for each windows O/S. Check it out here and try the one
I have no idea why this is so hard to find on the standard MS
Data Access pages.
07-11-2002, 11:30 AM
Already tried it and still nothing.
07-11-2002, 11:42 AM
Just to verify, you got the SP6 version and not the SP3 version?
This is quite new and not found on www.microsoft.com/data
07-11-2002, 11:46 AM
Well, looking back over the thread I see that you did already try
the right one so sorry for bringing it up again. Not sure what else