Problem deploying VB 6.0 app

**Stephane Richard** · Jul 17 '05, 07:48 PM

Re: Problem deploying VB 6.0 app

You might want to make sure that you installed (upgraded) MDAC on both
machines to version 2.6 (or higher if any).

--
Stéphane Richard
Senior Software and Technology Supervisor

http://www.totalweb-inc.com

For all your hosting and related needs

"Shashank Date" <sdate@everestk c.net> wrote in message
news:4e73d99bb2 e6d50e35ef62e7e 6087eaf@free.te ranews.com...[color=blue]
> VB Gurus,
>
> I have developed a VB 6.0 application on WIN XP Pro which I am trying to
> deploy on another machine on the network which is running Win 2000 Pro.
>
> I am using the "Package & Deployment wizard" that comes with the Visual
> Studio 6.0 Toolset to deploy it on a shared folder.
>
> Everything seems to go fine until I run the app ... then it does ** not[/color]
show[color=blue]
> any data ** in the DataGrid controls. No errors are generated either. I[/color]
have[color=blue]
> bound the DataGrid to ADODC which uses Excel Spreadsheet DSNs (all of[/color]
which[color=blue]
> I copy manually to the deployed folder).
>
> What am I missing ? I have included below, the contents of SETUP.LST
> generated by the wizard for reference. The thing that strikes as odd to me
> is in the [Setup] section it says: "DefaultDir=$(P rogramFiles)\My App". Why
> $(ProgramFiles) ?
>
> Thanks in advance.
> -- Shashank
>
> --------------------------------------------------------------------------[/color]
--[color=blue]
> -------------------------------------
> [Bootstrap]
> SetupTitle=Inst all
> SetupText=Copyi ng Files, please stand by.
> CabFile=MyApp.C AB
> Spawn=Setup1.ex e
> Uninstal=st6uns t.exe
> TmpDir=msftqws. pdw
> Cabs=1
>
> [Bootstrap Files]
> File1=@VB6STKIT .DLL,$(WinSysPa thSysFile),,,6/18/98 1:00:00
> AM,102912,6.0.8 1.69
> File2=@COMCAT.D LL,$(WinSysPath SysFile),$(DLLS elfRegister),,5/31/98 1:00:00
> AM,22288,4.71.1 460.1
> File3=@stdole2. tlb,$(WinSysPat hSysFile),$(TLB Register),,8/23/01 7:00:00
> AM,17920,3.50.5 014.0
> File4=@asycfilt .dll,$(WinSysPa thSysFile),,,8/23/01 7:00:00
> AM,77824,3.50.5 014.0
> File5=@olepro32 .dll,$(WinSysPa thSysFile),$(DL LSelfRegister), ,8/23/01[/color]
7:00:00[color=blue]
> AM,106496,5.0.5 014.0
> File6=@oleaut32 .dll,$(WinSysPa thSysFile),$(DL LSelfRegister), ,8/23/01[/color]
7:00:00[color=blue]
> AM,569344,3.50. 5014.0
> File7=@msvbvm60 .dll,$(WinSysPa thSysFile),$(DL LSelfRegister), ,8/23/01[/color]
7:00:00[color=blue]
> AM,1388544,6.0. 92.37
>
> [IconGroups]
> Group0=MyApp
> PrivateGroup0=T rue
> Parent0=$(Progr ams)
>
> [MyApp]
> Icon1="MyApp.ex e"
> Title1=MyApp
> StartIn1=$(AppP ath)
>
> [Setup]
> Title=MyApp
> DefaultDir=$(Pr ogramFiles)\MyA pp
> AppExe=MyApp.ex e
> AppToUninstall= MyApp.exe
>
> [Setup1 Files]
> File1=@RICHED32 .DLL,$(WinSysPa thSysFile),,,5/7/98 1:00:00
> AM,174352,4.0.9 93.4
> File2=@RICHTX32 .OCX,$(AppPath) ,$(DLLSelfRegis ter),$(Shared), 6/24/98[/color]
1:00:00[color=blue]
> AM,203576,6.0.8 1.69
> File3=@TABCTL32 .OCX,$(AppPath) ,$(DLLSelfRegis ter),$(Shared), 6/24/98[/color]
1:00:00[color=blue]
> AM,209192,6.0.8 1.69
> File4=@MSFLXGRD .OCX,$(AppPath) ,$(DLLSelfRegis ter),$(Shared), 6/24/98[/color]
1:00:00[color=blue]
> AM,244024,6.0.8 1.69
> File5=@msstdfmt .dll,$(AppPath) ,$(DLLSelfRegis ter),$(Shared), 4/5/01[/color]
12:43:19[color=blue]
> PM,118784,6.0.8 8.4
> File6=@MSDATGRD .OCX,$(AppPath) ,$(DLLSelfRegis ter),$(Shared), 6/24/98[/color]
1:00:00[color=blue]
> AM,260920,6.0.8 1.69
> File7=@MSCOMCT2 .OCX,$(AppPath) ,$(DLLSelfRegis ter),$(Shared), 6/26/98[/color]
1:00:00[color=blue]
> AM,644400,6.0.8 1.77
> File8=@MSADODC. OCX,$(AppPath), $(DLLSelfRegist er),$(Shared),6/24/98 1:00:00
> AM,118064,6.0.8 1.71
> File9=@msado10. dll,$(AppPath), $(DLLSelfRegist er),$(Shared),1 1/10/97[/color]
9:30:12[color=blue]
> PM,226064,1.0.1 .31
> File10=@MSBIND. DLL,$(AppPath), $(DLLSelfRegist er),$(Shared),6/18/98 1:00:00
> AM,77824,6.0.81 .69
> File11=@MyApp.e xe,$(AppPath),, ,7/5/03 1:06:18 PM,73728,1.0.0. 0
>
>[/color]

**Shashank Date** · Jul 17 '05, 07:48 PM

Re: Problem deploying VB 6.0 app

"Stephane Richard" <stephane.richa rd@verizon.net> wrote in message[color=blue]
> Those DSN files can they just be copied manually? or should you add them
> through the control Panel? or add them as services? Hmmm[/color]

I added them through the Control Panel. Still not difference.
I don't know how to add them as services.

But here is an interesting observation ... when I deleted one of the DSNs
on the source machine so that it could not be found at runtime, the form
which refered to it threw an "Unknown Error" exception.

When I did the same thing on the target machine, it did not throw any
error!!
Ran exactly like before ... looks like it does not even refer to the DSNs.

Isn't that strange ?
[color=blue]
> I'll need to do a little research....but except for the obvious EXE files
> and a few others....I thought everything else had to be "registered "[/color]
somehow[color=blue]
> on the machine.[/color]

You mean like registering the OCXs and DLLs and stuff ? I thought the
"Package & Deployment" wizard took care of that .. but then again, it may
not.
One more thing to check.
[color=blue]
> Stéphane Richard[/color]

Thank you so much.
-- Shashank

**Shashank Date** · Jul 17 '05, 07:48 PM

Re: Problem deploying VB 6.0 app

"Shashank Date" <sdate@everestk c.net> wrote in message
[color=blue][color=green]
>> I thought everything else had to be "registered " somehow
>> on the machine.[/color]
>
> You mean like registering the OCXs and DLLs and stuff ? I thought the
> "Package & Deployment" wizard took care of that .. but then again, it may
> not.
> One more thing to check.[/color]

Ok, I also did this ... registered every OCX and DLL used by my app using
regsvr32.exe. Some of them were already loaded in the memory, so
it asked me to use "Pview" (don't have it) to unload them. And of course,
I rebooted and all that good stuff. Still no go :-((

I am only trying to deploy from one Win XP to another Win 2K Pro.
I cannot imagine the nightmare of those who have to deploy across
thousands of machines with differing Win versions.

**Stephane Richard** · Jul 17 '05, 07:48 PM

Re: Problem deploying VB 6.0 app

as for the DSN yes the deployement wizard should take care of that,
essentially.... and if you have already dsn servers, then you shouldn't need
to install it as a service....I did the research and the DSN server is the
service that can understand/initiate whatever DSN needed by any application.

So I'm wondering what else could be tried....doing more reserarch.

--
Stéphane Richard
Senior Software and Technology Supervisor

http://www.totalweb-inc.com

For all your hosting and related needs
"Shashank Date" <sdate@everestk c.net> wrote in message
news:080cdf567f 5ee779ee3162a99 332ec76@free.te ranews.com...[color=blue]
>
> "Shashank Date" <sdate@everestk c.net> wrote in message
>[color=green][color=darkred]
> >> I thought everything else had to be "registered " somehow
> >> on the machine.[/color]
> >
> > You mean like registering the OCXs and DLLs and stuff ? I thought the
> > "Package & Deployment" wizard took care of that .. but then again, it[/color][/color]
may[color=blue][color=green]
> > not.
> > One more thing to check.[/color]
>
> Ok, I also did this ... registered every OCX and DLL used by my app using
> regsvr32.exe. Some of them were already loaded in the memory, so
> it asked me to use "Pview" (don't have it) to unload them. And of course,
> I rebooted and all that good stuff. Still no go :-((
>
> I am only trying to deploy from one Win XP to another Win 2K Pro.
> I cannot imagine the nightmare of those who have to deploy across
> thousands of machines with differing Win versions.
>
>[/color]

Problem deploying VB 6.0 app

Problem deploying VB 6.0 app

Comment

Comment

Comment

Comment