Randem Systems Support Board

I'm running in safe mode, so I cannot take files from system folder but as Innoscript didnt found msado21.tlb and showed in red colour, I copied the file in another folder.
 
I guess that the Os Updater check doesn't related with the files that Innoscript must include in the script but with the call to the exe.
 
I'd promise that before the update (comcheck said I had MDAC 2.6) there were no complains about msado21.tlb
 
Very very very thanks for your help. Now I can build the setup

munktaber,
 
Inno Setup is complaining about it because you are taking it from the system folder. you should not need to deploy it since you have updated your MDAC. you can just remove it from the script.

I,ve updated MDAC to 2.8 with your OS updater and all seems to be OK but now Inno Setup is complaining about msado21.tlb and I dont know if I must include it (as is a system file) or is installed with the OS updater.

Questions is what this board is for. We choose to develop on XP and test on lower versions. We think that is best.
 
If you are developing on 98 I would install MDAC 2.8 to make sure 98 is up-to-date.
 
You can't make sure of the MDAC version so I would always install the latest.

System files that I use seem to be related with data access.  
 
I think that the best option, as you say, will be to generate the script in safe mode and include  
the necessary to install MDAC instead of whole OS Updater.
 
In my opinion is preferable an automatic MDAC install rather than wait to an application failure which makes the user distrust.
 
Development computer is Windows 98 with MDAC 2.7 and the application must run on all Windows OS  (2000,XP, 98,ME,NT)
 
Would it be convenient to change development computer to Windows XP?
Should I  install MDAC 2.8?
How I may modify the script so that it installs MDAC 2.7 but not overwrites MDAC 2.8?  
 
Sorry  for so many questions

The reason you are suppose to copy the files from the system folder is to get you to research these files to make sure that they can be deployed as is.
 
Of course if you ignore this and deploy anyway without the research... youre own your own, we tried.
 
You can include the Auto OS Updater if you believe that it would benefit your app being installed on each machine it is attempted not matter if the user does not have their machine up-to-date in the areas of MDAC, DCOM and JET engines. If your app does not use databases etc then there is no need.
 
Yes, the installation should be distributed without the deleted files. dao360.dll suggest the you are using a database so distributing the MDAC might not be a bad idea or at least making sure the user knows where to download it if the app does not work on their machine.

Well, SF7 is Setup Factory 7. I didnt want make any kind of promotion on this.
Now I,ve compared the files included by SF7, VB Package&Deploymet and Innoscript and there some differences.
But in some XP machines that didnt work with the VB P&Deployment Wizard the script generated by Inno worked perfectly and about ten time faster [you are winning ]
 
I've copied the files on system folder to another folder and you can see the result in the attached file. I think that the deleted files belong to data objects. Then I have two question
1. Can I distribute the setup without that delete files or I should include the OS updater (huge)
2. Whats the difference between copy the unsafe files in other folder against use the unsafe mode.
 
Thanks in advantage
 
 
 

munktaber,
 
Thank you for your kind comments.
 
How did you run InnoScript and with what settings. If you run with some settings things like this are expected as per the manual.
 
What is SF7?
Are you running in SAFE MODE?
Did you place the additional search paths in the path area?
Can you zip and upload the .pjt and log files?

First of all, I must say you have a great application.
Well, my dude is this. I,ve runned innoscript and compare with SF7, this one get me some files (dll mainly) that not appears with InnoScript