ok.

In your existing parameters you probably had...

lparameters vcSomeVar

To accommodate for need via InstallShield, add some more to review and see what the pieces are... added 5 extra... don't know WHAT install shield is trying to send...

Then, first thing after the lParameters... copy memo to a text file to review in a bit... Since running via Install Shield, it won't be development mode for you to "SET STEP ON", analyze the values and figure out what is needed.

lParameters vcSomeVar, vcTest1, vcTest2, vcTest3, vcTest4, vcTest5

list memo like * to MyReviewFile.txt

... continue with rest of program

Ok. Now, look at the "MyReviewFile.txt" it may be that install shield is doing something stupid, or we just don't understand. Looking at the file, you may see that the parameters may be something like...

vcSomeVar = [']
vcTest1 = [TheFile]
vcTest2 = [exe]
vcTest3 = [']

Sounds stupid, but who knows...

Anyhow, once you understand what is being sent, you can assess and act upon it. You stated that the Windows "Shortcut" using the "path\file" using the double quotes works probably has the

vcSomeVar = "path\file" as expected... so...

if file( vcSomeVar )
  */ Assume from the shortcut and call form with this parameter
  do YourForm with vcSomeVar
else
  */ Appears to be from the InstallShield... rebuild the piece(s)
  */ that REALLY hold the values intended...
  lcRealValue = vcTest1 + "." + vcTest2
  do YourForm with lcRealValue

endif

Again... I don't know what InstallShield shoves into the initial parameters of the application... Maybe once you try the above approach and it still doesn't work, paste the text file here for me to review next cycle.


Don