Okay, this one is baffling even the people at Microsoft.

This one woman attempts to use the application as a guest. So she clicks on the icon and it attempts opening the files from the FMS as guest. It gets about 2 or 3 DBs open and she gets the error "Filemaker.exe has generated an error and will now close".

If anybody else logs onto her computer and runs the application it works fine. No errors.

This led us to there being something wrong in her profile so we deleted her profile and tried again. Everything worked fine. Until she logged off and logged back on after lunch. Same thing.

She can go to another computer and logon and it works just fine there. It is only her on the machine at her workstation. So we changed computers. SAME THING.

I then believed she was customizing her computer with something like a screen saver. So I told her not to do anything but run the File Maker application. Once again, it broke.

I then tried loading FMP3.0 directly onto her computer (vice just the FM runtime environment). FMP will not run under her login.

The exact error is c0000005.

Like I say, anybody else can logon to her computer and it works no problem.

I contacted MS since this is a brand new computer with Windows2k on it, trying to find out about that error and how the profile could be generating it. They haven't been able to figure it out yet either.

Anybody here ever seen this error with FM?

IMHO FM is certified for W2k from version 5.

That's true, and that is probably a lot of the problem with this set up. 3.0 is only certified thru W95.

However the client app works on all the other W2K machines. That is why her case is baffling.

Persistance and a new view point.

After much pounding of heads on the monitor, one guy looked at the PRINTER DRIVERS installed on the machine. He found a bogus one. We removed it and the problem went away. WOW! Apparently the application was trying to call this bogus printer and crashing.

Hey congrats!

That will definitely do it!

Just amazing that it was crashing FM vice just refusing to print. Actually she wasn't even trying to print from FM. She was trying to print from another application and then when she would come back to FM it would crash.

Weird.

FM will even crash when opening, if there are printers whose names are too long, etc., even when they aren't the default.

Hmmmm Is FM working on fixing this "little" bug?