Randem Systems Support Board

Yes, add the Jet files after that MDAC. The last MDAC that had the JET engines in it was MDAC 2.5 but you also need the DAO from MDAC 2.0.
 
The lines for the JET 3.51 should look something like this:
 
[Files]
Source: c:\server data\Randem\Develop\Support\Jet35sp3.exe; DestDir: {tmp}; Flags: ignoreversion; MinVersion: 4.0,4.0
 
[Run]
Filename: {tmp}\Jet35sp3.exe; Parameters: /Q; WorkingDir: {tmp}; Flags: skipifdoesntexist; MinVersion: 4.0,4.0

thanks for the replies  
 
1) MDAC - that seems clear
 
2) Jet35sp3.exe - I have downloaded that from the MS website
[http://support.microsoft.com/kb/172733/EN-US/]
 
Since the files in are newer than MDAC20, I assume that I should add it after the MDAC2.
 
Should I use the same flags as for MDAC?

Yes, I am missing Jet 3.51 on the site but you can google for Jet35sp3.exe. This would be the file for that.

The difference in the runtime files is correct. There are universal runtime files and you would be using the OS specific ones (Not Good). The ones with InnoScript are the ones that should be used. The one that is deployed in the VBrun60sp3 file is newer but will not work on all OS's, the one in InnoScript will work in all OS's.
 
The MDAC 2.0 file should be deployed to the {tmp} folder and then deleted after installation. I would use a template to add these lines into the script as such:
 
[Files]
Source: c:\program files\randem systems\innoscript\innoscript 9\osupdaters\mdac_typ_20.exe; DestDir: {tmp}; Flags: deleteafterinstall ignoreversion nocompression;
 
[Run]
Filename: {tmp}\mdac_typ_20.exe; Parameters: /Q /C:setup /QNT; WorkingDir: {tmp}; Flags: skipifdoesntexist; MinVersion: 4.0,4.0

One more question
I'm including the file 'mdac_typ_20.exe' as I think this is the one needed for DAO/Jet 3.51.
 
I've used the 'Add files' area to do this. Innoscript desides that this should be installed into {app} directory - even if I choose {sys} from the drop down list.
 
Source: c:program filesrandem systemsinnoscriptinnoscript 9osupdatersmdac_typ_20.exe; DestDir: {app}; Flags:  uninsneveruninstall restartreplace sharedfile;
 
Is this correct?

BTW did you realise that one of the VB runtime distribution files, msvbvm60.dll, that comes with InnoScript, is a different version to that in the file VBrun60sp3 [downloaded from your website]
 
In VB6 Redist Files: 03/09/02   v 6.0.96.90
In VBrun60sp3:    23/02/04   v 6.0.97.82
 
will this be a problem?

If you want not to deploy the big version (ALL) then you can place in your script the Jet 3.51 and DAO installations separately.
 
Ah - I think then that I only need the separate installation file 'Microsoft Data Access Components 2.0 (5.1mb)' .  I see from digging into your notes, this is the 'Last MDAC that had Jet 3.51 support'.
 
If I'm not selecting the correct installation please can you tell me which one I should use - there are lots of installations on your site for Jet 4.0, but none that explicitly state for Jet 3.51...

Just to confirm - the updater will also handle the MSVCRT40.DLL, msvcrt.dll, mfc42.dll & MFC40.DLL files?
 
No, those are Visual C   Runtime Files and should not be deployed seperately but should be deployed in a SP for VC   http://support.microsoft.com/kb/259403
 
Those files should have automatically have been removed from the script by InnoScript. If they haven't been you need to upgrade to the lates UnSafe.fil file for InnoScript or just upgrade to the latest version of InnoScript to get that file installed with it.

Vista does not need the Updater unless you are deploying DAO and/or Jet 3.51. If run on Vista then dao and Jet 3.51 files will be deployed.
 
If you want not to deploy the big version (ALL) then you can place in your script the Jet 3.51 and DAO installations separately.

One final question.
 
In Innoscript itself and on the website, I see that there are separate updaters for NT, 2000 and XP, but there does not seem to be a separate updater for Vista.  Is this correct?
 
Is the only way to update for Vista to use the complete 'All Versions' updater?

Further question...
 
should my client un-install the program before he runs the updater, and then re-install
or
can he just run the updater?

Thanks for the advice
 
Just to confirm - the updater will also handle the MSVCRT40.DLL, msvcrt.dll, mfc42.dll & MFC40.DLL files?

Aloha,
 
InnoScript automatically removes files that can be dangerous to deploy and that should not be deployed for there is a better safer way to deploy them. Add the Automatic OS Updater to the installation and it will take care of any MDAC/DCOM/JET issues for it will deploy the appropriate files for the correct OS. You should not ignore what InnoScript does for it can be disastrous https://randemsystems.support/multi-database-control-%28rsdbcontrol%29/database-problems/. There are also other files that should not be deployed and InnoScript will help you there with what should be deployed instead. Run InnoScript on you VBP file, it will do a better job that running it from PDW's setup.lst file.

I'm hoping that you can give me a spot of advice.
 
I have a PDW setup for a VB6 program that uses DAO 3.51.
 
The PDW setup includes a number of files that seem to be ignored by InnoScript [when running in PDW mode or in VBP mode]:
 
MSREPL35.DLL, MSRD2X35.DLL, expsrv.dll, vbajet32.dll, MSJINT35.DLL, MSJTER35.DLL & MSJET35.DLL
and
MSVCRT40.DLL, msvcrt.dll, mfc42.dll & MFC40.DLL
 
The install really does need these files    
 
Have I missed anything or done something silly?
 
Is there a way to persuade InnoScript to pick these up automatically, or do I need to add them manually?
 
If I need to add them manually, can you advise on the proper flags.
 
Thanks for your help [and the useful program!]