I am having trouble getting the package and deployment wizard to run on a Win2000 client. I rarely use PDW and I have never used it on Win2000.
I get through the first screen (1 of 7, 2 of 7,etc...) and then it gives me some error and asks me to restart and thatís as far as it gets. Forgive me for the vague description of the error. I was hoping someone recognizes it and maybe has a solution.
The network admin has no idea and neither do I. I could Regsvr32 all the components but I need MDAC2.5 to install and provide Jet3.51 providers. I can't seem to get MDAC to install 3.51 but the PDW does. So thatís the problem.
There is only a couple clients with win2k, the rest are win98 (no problems there).
Anybody know how to get Win2000 to quit bothering me, off hand, that is. Or does anybody know how to get MDAC2.5 to add support for Jet3.51 instead of Jet4.0 if I install it separately?
Any help or point in the right direction will be appreciated.
Where did this forum come from? I did not even know it was here :)
For anybody who is interested I found a site with a few solutions to my problem.
It can be found HERE (http://www.tek-tips.com/gviewthread.cfm/lev2/4/lev3/32/pid/792/qid/99494)
05-13-2002, 12:31 AM
I've had this problem too.
Why do you need the 3.51 jet drivers?
They are not available in MDAC 2.5 and up, you need to go back to 2.1 to have them.
I'm using an Access 97 mdb file too in some apps and everything can be done using the 4.0 jet drivers, even creating of an Access 97 mdb file.
This should be the connection string when creating an Access 97 mdb file:
strConnection = "Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=" & sFileName & ";" & _
"Jet OLEDB:Engine Type=4;" ' <- to create an Access97 mdb file
Just to read and write to the Access 97 file you don't need to specify the engine type anymore.
strConnection = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & sFileName
The reason I need them is still a little unclear. Over the last couple years I have never found a definitive answer to which providers to use for Access97 or 2000. Most everything I read says to use 4.0 with Access 2000 and not 97 but there is never any real solid reasons behind it.
HERE (http://www.visualbasicforum.com/showthread.php?s=&threadid=26751) is a thread where I was trying to determine this very question.
With the project I am working on in that thread, I am going to use 4.0 with 97 for the first time but for this other project I am reading and writing to the mdb and don't want to take any chances until I have more conformation on the subject. If you could add your knowledge to that thread I would appreciate it.
I always tried to stay away from any DB apps (very boring to me) and it is catching up to me now. From installers to providers to the troublesome Data Environment Designer, the little problems are driving me crazy. I spend 10 hours on the code and 20 on solving little quirks with ActiveX.
Although I think I can solve the PDW/Win2k problem I am still interested in why it is giving me problems. My old employer had several installers for me to use but now I have the PDW and Inno to choose from until I purchase some better ones. I have not tried Inno yet on this app but would like to stay away from freeware for my serious projects, just incase...
BTW You said you had a similar problem too, did you solve it by just going with Jet4.0 or did you find another fix?
05-13-2002, 01:30 AM
I fixed it all using the Jet 4.0 driver because it's backwards compatible with 3.51. Only when creating a '97 MDB from scratch you have to specify the engine type, like I did in the example connection string.
So at the moment I distribute MDAC 2.5 (sometimes with DCOM95 or DCOM98) and use the P&DW to install my application.
Haven't had any problems since.
(I'm not to fond on database programming either ;))
05-13-2002, 06:54 AM
I agree with Arnout and believe that as long as all you are doing
is reading and writing to existing tables in the .mdb, the 4.0
provider won't cause any problems.
I solved the PDW Win2K problem last week. The 2000 workstations did not have service packs installed. I installed SP2 on them and the installer worked like it was supposed to. I guess that was one of the bugs with Windows 2000.