Can't open runtime solution

[DykstrL]

What OS version? Is your client also using Office? - what version?

Windows 2000 and Office 2000 or XP installed will sometimes do strange things to unknown extensions, like decide that it is a "Word fast-file", whatever that is, or it decides that the runtime files are Adobe Acrobat files. The extension for the "Word fast-file" does not show up in the File Types list - in other words, it's hidden. You can only see it by opening the Registry. When this happens, the only resolution is to find the offending Registry entry, delete it, then run the EXEcutable of your solution to re-register the extension.

I distribute a FileMaker runtime solution on CD and on the web and I was having this problem with a lot of W2K machines. I now include the registry fix file in the system folder of the solution. When I get a support call for this problem, I just have them run the registry fix file - and all is well.

I would send you a copy of the fix file, but I use ".WF9" extension for my solution so it won't help you, but this is what the registry fix would look like for your situation:

[HKEY_CLASSES_ROOT.USR]

@="FMPro50Run.USR"

"Content Type"="application/filemaker"

Hope it helps...

[ April 04, 2002, 02:28 PM: Message edited by: dykstrl ]

[summergirl]

quote:

---

Originally posted by dykstrl:

What OS version? Is your client also using Office? - what version.

---

She ordered Win 98 OS, because I specifically said that FM still doesn't support XP. I don't for sure, but I'd bet she's using Office, but which version is unknown...

Another strange thing: I thought if you ran the solution from a server to a networked workstation, you have to have access the file using FileMaker Pro. She said she doesn't have FileMaker installed on the workstation or the server. Yet she's been running it this way for a year. Can you explain THAT? Could it be part of the problem? (But if so, why would the older machine networked to the same server work just fine?)

Thanks for sending the registry fix info. Unfortunately, I have no idea what you're talking about!

Mary Z

[DykstrL]

Runtime solutions can be installed and run from a fileserver, but the files are not multi-user. Only one person at a time is able to access it.

My runtime solutions work fine on all flavors of Windows from 95 to XP Professional.

You stated that the file icons look different. That indicates to me that your problem is a Registry issue that can only be fixed by modifying the machine's registry.

A little background: The first time you run your runtime solution (the EXE file), the runtime engine checks the Registry to see if the extension is registered. If not, it enters a registry entry to say that the file extension contained in the EXE file (in your case, "USR") is now associated with your EXE solution file.

If there is another association for that extension, FileMaker does not overwrite the entry. If the association is not listed in the File Types list, the only way to fix this is to find the entry in the Registry and either modify it or delete it completely.

Since you don't know what I'm talking about, I suggest that you find a friend or co-worker savvy in computers who can create a registry file for you - it's not for the timid.

If you send me your email address, I will send you a registry file that MAY fix the problem - no guarantees.

[ April 04, 2002, 03:07 PM: Message edited by: dykstrl ]

[summergirl]

A client has been using my runtime solution without problems for a year.

A month ago she bought a new computer. After 2 weeks, my solution stopped working; "illegal operation" screens kept popping up. She found and resolved a conflict with an HP printer driver by reformatting the HD. The runtime solution worked fine again.

Today when she tried to run the solution, an illegal operation screen comes up, with the notation that the "MSVCRT.DLL file is corrupt."

-Deleting and reinstalling the bad .dll file does not work.

-Reinstalling the solution folder (including .dll files) from the original CD does not work. One strange thing is the .USR files now have the same icon as the .EXE file...

The same solution, accessed from a common server, works fine on a different machine.

Any ideas on this one? Thanks in advance for your expert advice!

Mary Z

[summergirl]

Here's the final chapter in this story. My client resolved the runtime problem. Here's her email explanation:

"Just for your info on the nightmare we have been through - the model HP4050 laserjet printer has a driver that conflicts with Filemaker Pro and you need to use the 4 plus driver that is in the operating system disk. Do not use the drivers for the printer that are on the net. They will not work."

Case closed.

Mary Z