Randem Systems Support Board

OK thanx for the info.... I guess all my problems already solved in this topic... Thank you randem!! Viva InnoScript!!

That is beyond the scope of InnoScript. You would need to research MSDE to see if it can be done via code. If so then you may be able to write a program to do what you want and run that after you run the MSDE installation. It is your app connects to the MSDE database so that should not be an issue.

How can I attach database after the end of installation? Looks like needs more script in MSDE and can InnoScript handle it in external installs?

You would need to install the MSDE Engine using the MSDE installation. You can just add the database files to your installation

okay.... thanks for the info.... I have success instaling in Windows 7, ComponentOne also success.
 
I have one question, how can I install MSDE and also attaching the database automatically using InnoScript?

You can't just click WinSxS to get a WinSxS Deployment (as in the manual). It is best if you get you application to work in regular mode first because when you have trouble creating the WinSxS deployment you will know that the application works and possibly where to make the corrections...

I can't click WinSxS button.... why it is happen?

hmmm.... I think that WinSxS is more comfortable in whatever OS'es right? But if I choose WinSxS and what happen to my DLL or OCX that needs to register? my application might not working smoothly?

WinSxS is an installation that does not need to register any dll/ocx and creates a manifest file that the application uses to access those files. In this type of installation all dll/ocx files that the application needs would be deployed to the {app} folder and the application would find them there when it needs them. This type of installation is used so that if the user has another installation of components you are deploying your application would not interfere with the operation of those program that use a different version of those files.
 
The other installation types are just preferences. You are installing a Release for your application or an Update and that name will appear on the exe created by the script so that you can track what you are doing if you create multiple installation types.

what is WinSxS? I don't understand between Release, None, Update, WinSxS

Not necessarily... If you were doing a WinSxS installation you probably should but the destination {sys} is fine in this case.

Ohhhh... then I should change the DestDir to: {app} right? Cause I want to install it in Windows 7 Home Basic
 
 
[Files]
Source: C:WINDOWSsystem32tidate8.ocx; DestDir: {sys}; Flags: restartreplace sharedfile;
Source: C:WINDOWSsystem32tinumb8.ocx; DestDir: {sys}; Flags: restartreplace sharedfile;

Yes... But you really should not deploy the files from the system folder you may get into trouble down the line as I already suggested.

This is my ComponentOne.tpl :
 
[Files]
Source: C:WINDOWSsystem32tidate8.ocx; DestDir: {sys}; Flags: restartreplace sharedfile;
Source: C:WINDOWSsystem32tinumb8.ocx; DestDir: {sys}; Flags: restartreplace sharedfile;  
 
[Run]
Filename: {app}c1regsvr.exe; Parameters: /u tidate8.ocx; Flags: skipifdoesntexist; WorkingDir: {app}
Filename: {app}c1regsvr.exe; Parameters: /u tinumb8.ocx; Flags: skipifdoesntexist; WorkingDir: {app}
 
Is it correct?

Yes... Well, add in front of the [Run] Section