1 Attachment(s)
[RESOLVED] Vb6 Installation Freezes At Mdac 2.0 Dialog
Hello everybody,
I made a setup using PD wizard. When I tried to install it in the system which the project & setup was made, the installation proceeds upto MDAC 2.0 dialog and stays there for eternity. I open the task manager and END the non responding MDAC 2.0. I get "NTVDM.EXE has caused an error" etc with SEND & DONT SEND. I click send another dialog opens
Quote:
The request to end the selected 16 bit task has timed out. The Win16 Subsystem may be unstable. Press OK to terminate the win 16 sub system or cancel to leave it running
I click ok and the installation continues....Can somebody show what could be wrong.
My project uses Access 2003 as DB, DTPs, MSFlxgrds in the project.
Re: Vb6 Installation Freezes At Mdac 2.0 Dialog
Why are you using MDAC 2.0? Its so old. Try upgrading to MDAC 2.8. Do you also have SP-6 installed for Visual Studio?
Re: Vb6 Installation Freezes At Mdac 2.0 Dialog
Quote:
Do you also have SP-6 installed for Visual Studio?
Yes I supose. The splash screen at startup of VB6 states so.
Quote:
Why are you using MDAC 2.0? Its so old
I have no choice...meaning in the first place I did not add mdac 2.0, it was added automatically I suppose, during pdw. Any idea how do I add mdac 2.8
Re: Vb6 Installation Freezes At Mdac 2.0 Dialog
The P&D Wiz determines the MDAC being used and packages it. It opens the .vbp file and reads the reference to MDAC. So if you open your project update the mdac reference, test, and if all is well then package, it will be 2.x that you upgraded to.
Re: Vb6 Installation Freezes At Mdac 2.0 Dialog
Are u by any chance referrring to the MS ADO 2.8 Library in the references section. What is MS ADO Recordset 2.8 Library?
Re: Vb6 Installation Freezes At Mdac 2.0 Dialog
Also if I use MSADO 2.8 would it not fail in a system which does not have 2.8?
Re: Vb6 Installation Freezes At Mdac 2.0 Dialog
No, buy selecting ADO reference in your vbp the p & d wiz packages and installs that version when you install on other systems.
Re: Vb6 Installation Freezes At Mdac 2.0 Dialog
OK what is MS ADO Recordset 2.8 Library?
Re: Vb6 Installation Freezes At Mdac 2.0 Dialog
It should be "MS ActiveX Data Objects 2.8 Library" which is a part of "Microsoft Data Access Components" (MDAC) ;)
Re: Vb6 Installation Freezes At Mdac 2.0 Dialog
I changed the ref to 2.8 still the installation freezes, even in the system where I am developing the sw??????
Re: Vb6 Installation Freezes At Mdac 2.0 Dialog
Note the dialog caption is still MDAC 2.0 setup
Re: Vb6 Installation Freezes At Mdac 2.0 Dialog
Did you make sure 2.0 was removed? Are you using any bound data access controls bound with 2.0? also, try recreating the package as the 2.0 is probably still in there.
Re: Vb6 Installation Freezes At Mdac 2.0 Dialog
Quote:
Did you make sure 2.0 was removed?
Yes
Quote:
Are you using any bound data access controls bound with 2.0?
No
Quote:
try recreating the package
I recreated using None but problem persists. I still get MDAC 2.0 setup dialog installation freezes, in the task manager I get Not responding
I use acs 2003 db,DTpick, MsFlex grid, SSTab, other than the std controls, MDI
Re: Vb6 Installation Freezes At Mdac 2.0 Dialog
NTVDM.EXE sounds familiar. Are you packaging on XP and installing on Windows 98 or ME? If so that is the problem.
Re: Vb6 Installation Freezes At Mdac 2.0 Dialog
I created the proj/setup on XP and tried to test install in the same XP sys when this problm shot up.
I tried to install in another sys (XP) no error occured!
Re: Vb6 Installation Freezes At Mdac 2.0 Dialog
Maybe its something on the system then and not the package.
Re: Vb6 Installation Freezes At Mdac 2.0 Dialog
would I have to re install VS or worse format sys?? to rectify the problem
Re: Vb6 Installation Freezes At Mdac 2.0 Dialog
Do you have some other system with VB on it that you could create a new package from and see if it works using that package. If so then reloading your VB or system would be a good idea.
Re: Vb6 Installation Freezes At Mdac 2.0 Dialog
I assume it was a problem with my system. I formatted the sys and reinstalled VB. Now it is working fine. Thankyou very much Mr. Rob