Runtime Can't find Primary File?

[fillies]

I have a solution bound on PC for PC. When using the Runtime Solution, the first time I try to run a script that creates a related record, I get an error message that says the (Primary file) cannot be found. After I select the right file, it works fine. I suspect that this has something to do with the file extension. (I used the default). If I don't remember to create a new related record in the runtime before delivering it to users, they are confronted with the error message, which means nothing to them. Would using a different file extension help? I tried using .fp5 but was told that is reserved for FM.

[David McKee (Protolight)]

Did you rename the file(s) in Explorer? (This includes changing the file extension yourself).

What vers of Developer tool are you using? From FMD4?

[fillies]

Nope, I didn't rename any files or extensions. I'm using Developer 5. The only thing I did regarding naming is I edited the default name of the solution that the Wizard presented.

[DykstrL]

What O/S version? Windows 2000 will not register the runtime extension if the user does not have permission to install software or modify the system - the registry on the machine is locked in this case, not allowing any changes. A lot of IT shops are using this 'feature' in W2K to try to lock down the desktop and reduce problems.

The first time the "EXE"ectuable of the runtime package is run, it checks to see if the extension is registered. If not, it adds (or tries to add) the extension to the HKEY_CLASSES_ROOT. If the registry is locked down, FM won't "find" any of the secondary files.

I am having the same problem with W2K users, so I have notices and warning messages on our web site and the install package that user need to be logged onto the machine as "administrator" to install the package - it's the only safe way.

[SteveB]

I believe that this is a longstanding FM bug. I have the same problem with the same message. I looked high and low, but since it only happens when I bind the solution, it probably is FM itself. I've got 2 occurences that I correct by running the bound version once, which properly initializes the filename path for ever more.