Randem Systems Support Board

InnoScript => InnoScript - General Questions, Report Bugs, Problems etc... => Topic started by: John Kim on March 17, 2004, 10:28:41 AM

Title: VB App distribution problem
Post by: John Kim on March 17, 2004, 10:28:41 AM
Hello,
 
I need a help.
 
I developed an application using VB6 and Access 97 DB, and implemented report  
module using Crystal Report 4.6(comes with VB6 package).  On a development  
machine(MS XP), everything worked fine including CR preview and printing as well  
as DB activities.  So using InnoSetup and InnoScript, I made a distribution  
package including runtime files for VB and CR (I included your  
VB_DCOM_MDAC_JET_Autosetup file to take care of database access runtime files),  
and tried on a FRESH XP machine(i.e., factory setting. I call test machine).  
All DB activities worked fine but CR had problems.  Right after  
CrystalReport1.Action = 1 is executed, series of run time error reports popped  
up:
     - CAN NOT CREATE DAO DBEngine
     - Error 20534: Error detected by  database DLL
 
My findings are:
 - On a test machine, after the error occured, if I install VB6 CD, everything  
worked fine (note that VB6 was just installed not executed)
 - Compared the DLLs loaded on the momory, before VB6 was not installed and  
after the VB6 was installed, found that the following 4 DLLs were missing in the  
NON-WORKING case:
 
    DAO350.DLL, MSJET35.DLL, MSVCIRT.DLL, MSVCRT40.DLL
 
But these files were in the system before or after VB6 was installed.
For some reason, these files were loaded if VB6 was installed. But I
don't know why these were not loaded, and how can I fix this without installing  
VB6 on a client machine.
 
Please let me know if you can resolve this issue.
 
 
Thanks,
John
Title: VB App distribution problem
Post by: Admin on March 17, 2004, 10:58:36 AM
John Kim  
 
If you want DAO350 to be picked up by InnoScript you will have to reference it in your project. once DAO350 is referenced in your project the jet engines that are dependencies of DAO350 will be picked up.
 
I do not see why you would need MSJET35.DLL unless you are accessing an Access 97 database.
 
The other two files you might want to check on the microsoft website to see if those two files should be deployed.
Title: VB App distribution problem
Post by: John Kim on March 17, 2004, 02:31:56 PM
I run the InnoScript against MS PDW file and found new dependency on DAO350. DAO350 need vb5db.dll.  After I include these DLLs. The problem was resolved.   By the way, I need MSJET35.DLL since I used Access97 DB.
 
InnoScript and InnoSetup are great tools!
In my experience, should use together with PDW since PDW has accurate dependency information.
 
You guys are great!!!!
 
Thanks,
John
Title: VB App distribution problem
Post by: John Kim on March 17, 2004, 02:33:41 PM
I should change my face.
Title: VB App distribution problem
Post by: Admin on March 17, 2004, 05:12:43 PM
John Kim
 
Running InnoScript against the VBP file would find the same dependencies if the search path has all the paths to search for the dependencies. This is controlable to limit/expand where InnoScript will search for files (for speed). You do not need PDW at all if you use the correct search paths.
Title: VB App distribution problem
Post by: Greg Lloyd (Unregistered Guest) on June 08, 2004, 08:54:22 PM
Thank you for InnoScript - it is great.
 
Just one question. When I run Innoscript in safe mode I get many missing files because VB6 installed most of the files (example msflxgrd.ocx) in the {win}\system32 folder.
 
Could you please comment on the log file contents in terms of safety. (My system is W2K and VB6 SP6)
 
Thanks.
 
[color=aa00aa]Randem Systems, Inc. - InnoScript - Version 2.3.9
 
 
9/06/2004 4:41:05 PM - Saving Settings... Please Wait
9/06/2004 4:41:05 PM -       Dependency File Processing
 
 
9/06/2004 4:41:05 PM - Procesing VB Runtime Files...
9/06/2004 4:41:05 PM -    MSVBVM60.DLL
9/06/2004 4:41:05 PM -    OLEAUT32.DLL
9/06/2004 4:41:05 PM -    OLEPRO32.DLL
9/06/2004 4:41:05 PM -    ASYCFILT.DLL
9/06/2004 4:41:05 PM -    STDOLE2.TLB
9/06/2004 4:41:05 PM -    COMCAT.DLL
9/06/2004 4:41:05 PM - Procesing Special Files...
9/06/2004 4:41:05 PM -    eAppointment.exe
9/06/2004 4:41:05 PM - Procesing VBP Project File...
9/06/2004 4:41:05 PM - eAppointment.exe   Dep - C:\My Documents\VB6_Current\eAppointment Jpeg\eAppointment.dep   
9/06/2004 4:41:05 PM - dao360.dll   Dep - C:\Program Files\InnoScript 2.3\VB6Dep.ini   
9/06/2004 4:41:05 PM -    MSJET40.DLL
9/06/2004 4:41:05 PM -    MSJTER40.DLL
9/06/2004 4:41:06 PM -    MSJINT40.DLL
9/06/2004 4:41:06 PM -    MSJTES40.DLL
9/06/2004 4:41:06 PM -    VB5DB.DLL
9/06/2004 4:41:06 PM - scrrun.dll   Dep - C:\WINNT\system32\scrrun.dep   
9/06/2004 4:41:06 PM -    MSVCRT.DLL
9/06/2004 4:41:06 PM - msstdfmt.dll   Dep - C:\WINNT\system32\msstdfmt.dep   
9/06/2004 4:41:06 PM - msflxgrd.ocx   Dep - C:\WINNT\system32\msflxgrd.dep   Microsoft FlexGrid Control 6.0 (SP6)
9/06/2004 4:41:06 PM - mscomct2.ocx   Dep - C:\WINNT\system32\mscomct2.dep   Microsoft Windows Common Controls-2 6.0 (SP6)
9/06/2004 4:41:06 PM - mscomctl.ocx   Dep - C:\WINNT\system32\mscomctl.dep   Microsoft Windows Common Controls 6.0 (SP6)
9/06/2004 4:41:07 PM - TABCTL32.OCX   Dep - C:\WINNT\system32\TABCTL32.dep   Microsoft Tabbed Dialog Control 6.0 (SP6)
9/06/2004 4:41:07 PM - MCI32.OCX   Dep - C:\WINNT\system32\MCI32.dep   Microsoft Multimedia Control 6.0 (SP3)
9/06/2004 4:41:07 PM - comdlg32.ocx   Dep - C:\WINNT\system32\comdlg32.dep   Microsoft Common Dialog Control 6.0 (SP6)
9/06/2004 4:41:07 PM -  
 
 Restart Dependency check for new items - 1
 
9/06/2004 4:41:07 PM - MSJET40.DLL   Dep - C:\Program Files\InnoScript 2.3\VB6Dep.ini   
9/06/2004 4:41:07 PM -    VBAJET32.DLL
9/06/2004 4:41:07 PM -    EXPSRV.DLL
9/06/2004 4:41:07 PM -    MSWSTR10.DLL
9/06/2004 4:41:07 PM -    MSWDAT10.DLL
9/06/2004 4:41:07 PM -    MSRD2X40.DLL
9/06/2004 4:41:07 PM -    MSRD3X40.DLL
9/06/2004 4:41:07 PM -    MSREPL40.DLL
9/06/2004 4:41:07 PM - MSJTER40.DLL   Dep - C:\Program Files\InnoScript 2.3\VB6Dep.ini   
9/06/2004 4:41:08 PM - MSJTES40.DLL   Dep - C:\Program Files\InnoScript 2.3\VB6Dep.ini   
9/06/2004 4:41:08 PM - VB5DB.DLL   Dep - C:\Program Files\InnoScript 2.3\VB6Dep.ini   
9/06/2004 4:41:08 PM -  
 
 Restart Dependency check for new items - 2
 
9/06/2004 4:41:08 PM - VBAJET32.DLL   Dep - C:\Program Files\InnoScript 2.3\VB6Dep.ini   
9/06/2004 4:41:08 PM - EXPSRV.DLL   Dep - C:\Program Files\InnoScript 2.3\VB6Dep.ini   
9/06/2004 4:41:08 PM - MSWSTR10.DLL   Dep - C:\Program Files\InnoScript 2.3\VB6Dep.ini   
9/06/2004 4:41:08 PM - MSWDAT10.DLL   Dep - C:\Program Files\InnoScript 2.3\VB6Dep.ini   
9/06/2004 4:41:08 PM - MSRD2X40.DLL   Dep - C:\Program Files\InnoScript 2.3\VB6Dep.ini   
9/06/2004 4:41:08 PM - MSRD3X40.DLL   Dep - C:\Program Files\InnoScript 2.3\VB6Dep.ini   
9/06/2004 4:41:08 PM - MSREPL40.DLL   Dep - C:\Program Files\InnoScript 2.3\VB6Dep.ini   
9/06/2004 4:41:08 PM - Creating Inno Setup File...
9/06/2004 4:41:08 PM -  
 
               Processed in UNSAFE file mode
 
               Files included in Script
 
          Version      OS       File
 
9/06/2004 4:41:08 PM -      6.0.97.82             Win32    C:\Program Files\InnoScript 2.3\VB6 Runtime\msvbvm60.dll
9/06/2004 4:41:08 PM -    2.40.4275.1          NT-Win32    C:\Program Files\InnoScript 2.3\VB6 Runtime\oleaut32.dll
9/06/2004 4:41:08 PM -     5.0.4275.1             Win32    C:\Program Files\InnoScript 2.3\VB6 Runtime\olepro32.dll
9/06/2004 4:41:08 PM -    2.40.4275.1          NT-Win32    C:\Program Files\InnoScript 2.3\VB6 Runtime\asycfilt.dll
9/06/2004 4:41:08 PM -    2.40.4275.1          NT-Win32    C:\Program Files\InnoScript 2.3\VB6 Runtime\stdole2.tlb
9/06/2004 4:41:08 PM -    4.71.1460.1          NT-Win32    C:\Program Files\InnoScript 2.3\VB6 Runtime\comcat.dll
9/06/2004 4:41:08 PM -        0.9.0.2             Win32    C:\My Documents\VB6_Current\eAppointment Jpeg\eappointment.exe
9/06/2004 4:41:08 PM -    3.60.6508.2          NT-Win32    C:\Program Files\Common Files\Microsoft Shared\DAO\dao360.dll
9/06/2004 4:41:08 PM -     4.0.7328.0          NT-Win32    C:\WINNT\system32\msjet40.dll
9/06/2004 4:41:08 PM -     4.0.6508.0          NT-Win32    C:\WINNT\system32\msjter40.dll
9/06/2004 4:41:09 PM -     4.0.6508.0          NT-Win32    C:\WINNT\system32\msjint40.dll
9/06/2004 4:41:09 PM -     4.0.7328.0          NT-Win32    C:\WINNT\System32\msjtes40.dll
9/06/2004 4:41:09 PM -      6.0.81.69          NT-Win32    C:\WINNT\system32\vb5db.dll
9/06/2004 4:41:09 PM -     5.6.0.6626             Win32    C:\WINNT\system32\scrrun.dll
9/06/2004 4:41:09 PM -  
 
* * * * * msvcrt.dll Deleted from script - UnSafe File * * * * *
 
9/06/2004 4:41:09 PM -      6.1.97.82          NT-Win32    C:\WINNT\system32\msstdfmt.dll
9/06/2004 4:41:09 PM -      6.1.97.82          NT-Win32    C:\WINNT\System32\msflxgrd.ocx
9/06/2004 4:41:09 PM -      1.0.0.213             Win32    C:\My Documents\VB Bits\Buttons_Cool_Dynamic\coolbutton.ocx
9/06/2004 4:41:09 PM -      6.1.97.82          NT-Win32    C:\WINNT\System32\mscomct2.ocx
9/06/2004 4:41:09 PM -      6.1.97.82          NT-Win32    C:\WINNT\System32\mscomctl.ocx
9/06/2004 4:41:09 PM -      6.1.97.82          NT-Win32    C:\WINNT\System32\tabctl32.ocx
9/06/2004 4:41:09 PM -      6.0.84.18          NT-Win32    C:\WINNT\System32\mci32.ocx
9/06/2004 4:41:09 PM -      6.1.97.82         DOS-Win32    C:\WINNT\System32\comdlg32.ocx
9/06/2004 4:41:09 PM -     6.0.1.9431             Win32    C:\WINNT\system32\vbajet32.dll
9/06/2004 4:41:09 PM -    6.0.72.9589             Win32    C:\WINNT\system32\expsrv.dll
9/06/2004 4:41:09 PM -     4.0.6508.0          NT-Win32    C:\WINNT\system32\mswstr10.dll
9/06/2004 4:41:09 PM -     4.0.6508.0          NT-Win32    C:\WINNT\system32\mswdat10.dll
9/06/2004 4:41:09 PM -     4.0.7328.0          NT-Win32    C:\WINNT\system32\msrd2x40.dll
9/06/2004 4:41:09 PM -     4.0.6508.0          NT-Win32    C:\WINNT\system32\msrd3x40.dll
9/06/2004 4:41:09 PM -     4.0.6726.0          NT-Win32    C:\WINNT\system32\msrepl40.dll
9/06/2004 4:41:09 PM - Translating parameters...
9/06/2004 4:41:09 PM - Saving Inno Setup file... Please Wait
9/06/2004 4:41:09 PM -  
 
 
Script created: C:\My Documents\VB6_Current\eAppointment Jpeg\Inno Setup\eAppointment.iss
 
Number of files found: 29
Number of files not found: 0   (Shown in Red)
Number of files deleted: 1
Elapsed Time: 00:00:04
 
WARNING: UNSAFE FILES MAY BE IN THIS SCRIPT
 
Please view the log for more details on your files
[/color]
Title: VB App distribution problem
Post by: admin on June 08, 2004, 11:16:09 PM
Greg Lloyd,
 
Any file marked missing while in SAFE MODE should be because they are to be taken from the SYSTEM folders. This is not always a good chice to take them from there since some dll/ocx/exe from the system folder are Windows OS dependant and will corrupt another version of the Windows OS.
 
It is not your system that needs to be scrutinized, it is the deployment systems where the problems will occur if you take Win2K OS dependant files and install them on non Win2K machine.
 
You have to check the Microsoft website and see which files are installed with the OS and never deploy those files. Some files are installed with every OS and never need deployment. These files should be placed into your unsafe.fil file and InnoScript will automatically remove them each time.
 
Of course any file only deployed with VB6 should be re-deployed with your app. A copy of these files should be included in a seperate folder for control purposes in deployment.
Title: VB App distribution problem
Post by: Ralph Roberts (Unregistered Guest) on June 14, 2004, 10:09:08 AM
I found the following statement on the veritest web site:
An important Microsoft logo requirement is that apps must not register, reference count, uninstall, or overwrite any core components of the OS.
It appears the scripts I'm generating violate that requirement.  Am I missing something?  Thanks.
Title: VB App distribution problem
Post by: admin on June 14, 2004, 06:51:17 PM
Ralph Roberts,
 
No, you are not missing anything. The key phrase is Core Components. These are files that make the OS work and probably come with every version of the OS. Replacing these files could be disasterous for your OS. This is why SAFE MODE does not get files from the OS System folders.If you override this, you should really know what your are doing.
 
To redistribute core components, One should use the MS service packs for that. MS has already done the work.
Title: VB App distribution problem
Post by: nurbaya (Unregistered Guest) on January 10, 2005, 05:00:58 PM
hello, anybody can help me!
 
i have 2 reports that to be preview when i click one button. How can i preview only one at one time and after i close the first report, then next the second report will preview. Now, both report will be previewed at the same time using diff screen.
 
tq
Title: VB App distribution problem
Post by: admin on January 10, 2005, 05:06:37 PM
nurbaya,
 
I would like to help you but I have no clue of what you are asking about or what program you are using. In order to get help you need to be more exact in you questions and provide more information.
Title: VB App distribution problem
Post by: flowerjd (Unregistered Guest) on May 18, 2005, 10:28:56 AM
Help!
  I get an error message - that all fields must have valid entries, Inno Setup Input is empty.
 
Please, where is this field located, what is the title of the input box?
 
Thanks, jdf
Title: VB App distribution problem
Post by: admin on May 18, 2005, 10:42:03 AM
flowerjd,
 
What exactly are you reffering to? What software are you using (with version)? What field? Inno Setup?
 
Can't help unless you give good descriptions.
Title: VB App distribution problem
Post by: flowerjd (Unregistered Guest) on May 18, 2005, 02:59:51 PM
After entering info in the Parameter section of Innoscript, I have selected the VB6- program/VBP file folder, I press the OK and receive  the following error message:
   All fields must have valid entries,  Inno Setup Input is empty.
If I knew were to find this field I could put information into it.  However, I don't get a clue from either the printed help documentation or from the sceen menus.
JDF
Title: VB App distribution problem
Post by: admin on May 18, 2005, 03:20:30 PM
JDF,
 
You did not complete the main screen information for where you would like the .iss file to be created.
 
You have to select where your vbp file and put in a location for your .iss file that you want to create.
 
This information is in the documentation
 
Install InnoScript.     https://randemsystems.com/innoscript// (https://randemsystems.com/innoscript//)  
Install Inno Setup (InnoScript uses Inno Setup).     http://www.jrsoftware.org (http://www.jrsoftware.org)  
Select your vbp, exe, and application folder and the name of the output .iss file (.tpl file is optional).  
Press OK to convert your project file.  
Edit your script (.iss) with Inno Setup.  
Compile your script with Inno Setup.
Title: VB App distribution problem
Post by: flowerjd (Unregistered Guest) on May 19, 2005, 01:54:28 AM
Thank you for trying to help.  I have not seen any field which requested this information under the heading of Inno Setup output file.
I will attempt to attach a Word Doc to this response with samples of the screens presented.
Title: VB App distribution problem
Post by: admin on May 19, 2005, 02:01:29 AM
flowerjd,
 
 
You do have to create a InnoScript project first... File->New
Title: VB App distribution problem
Post by: flowerjd (Unregistered Guest) on May 19, 2005, 09:35:40 AM
I un-installed IS and deleted all files left, then re-installed.  The missing input screen now comes up.  Sorry, I guess the pic is attached didn't help you to see that a screen was missing.
JDF
Title: VB App distribution problem
Post by: Khawer (Unregistered Guest) on June 27, 2005, 07:10:55 AM
Hello,
    Please Help Me.
 
  I created a setup with Innosetup in which i included VB6 runtime files.In my machine setup work correctly but on other machine it gives an error.(Abort,Retry,ignore)  
       Please tell me how can i include VB6 runtime files in my setup.
                                 Thanks
Title: VB App distribution problem
Post by: admin on June 27, 2005, 07:26:49 AM
Khawer,
 
Please give more info on your situation. Did you use InnoScript? What does your script look like? etc...
Title: VB App distribution problem
Post by: bluestar (Unregistered Guest) on December 19, 2005, 12:24:15 AM
I need to deploy a vb6 project to win98, win2k and winXp and a xhttp.dll is required to registered in user computer, may i know to how to create a setup file using inno setup5
Title: VB App distribution problem
Post by: admin on December 19, 2005, 07:43:04 AM
bluestar,
 
InnoScript comes with a manual and Inno Setup has a help section that is in the program. You will need to read the instructions to get a general idea of how to use either.
 
What have you done so far...