>
What I did is set INSTALLDIR to be [CommonFileFolder]Vfp which I created in the Set INSTALLDIR window (that shows the list of folders). Then it was easy. I copied the .OCX file to this folder in the Files section of the InstallSheild tree and it seems to have done the job.>
>If I remember you were using a non MS OCX? If this is the case, I am curious as to how (if it was needed) ISE knew it needed to be registerd.
>
>SO - you're placing your runtime EXE and OCX objects in the same general destination folder?
>
>Interesting.
I remember looking up in the properties of the OCX (from within InstallSheild) and it was saying something to the effect that the file will be registered. I didn't have to specify anything. Maybe ISE figures it by the extention of the file?
I was not placing the .EXE and .OCX in the same folder. Actually the SETUP I was creating didn't have .EXE at all. This was a SETUP to install run-time DLLs only. So user didn't even have a dialog to enter or select destination directory.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
