Error c00000094

[sdocker]

I have an app being used by many people and 2 or 3 isolated cases where printing a report generates a c00000094 error. I believe it is happening on different printers, but it is always the same report.

Would deleting the foxuser files or PACKing the report file help?

I am using VFP 9.0 SP2.

Thank you,
Sam

 

[Mike Lewis]

Would deleting the foxuser files or PACKing the report file help?

Quite likely. Why not try it and see? It will do no harm, and may well solve the problem.

You might also check that you have the most up-to-date video and printer drivers.

More information:

http://fox.wikis.com/wc.dll?Wiki~C0000094Error

Mike



__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads

 

[sdocker]

Here is what I've done so far with no luck.

I broke the report into 4 parts and deleted a few lines at a time to determine if and when I removed something offensive, and the error stopped.

I am down to 4 reports with 2 lines of text or a rectangle and text box in each one.

Interesting thing is when I print to a PDF, 3 of the 4 reports are 6KB in size and 1 of them is 70KB. The entire original report is only 72KB.

I packed and checked the FRX file and it only has 13 records.

Any input would be helpful

Thanks,
Sam

 

[Mike Lewis]

So did you try the original suggestion of deleting the Foxuser files and packing the FRX? The Wiki reference I gave you suggested that as a possible solution.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads

 

[sdocker]

Not yet. I have to wait till the customer's IT person gets to it.

Sam

 

[sdocker]

Hi Guys,

I was finally able to resolve the problem. It turned out there was an old, no longer used font, (Letter Gothic), in the report. It was size 15.

Is it possible, as windows tried to replace it with a similar one, based on up to the 18 attributes a font possesses, and then re-size it, one of the calculation resulted in division by zero?

Whatever the reason, I think this incident should be disseminated, because in all the research i did regarding error c00000094, I never came across an issue that was caused by a font.

Sam

 

[Mike Lewis]

When you say the font was "no longer used", do you mean it was present in the report but not installed on the user's system?

If so, that shouldn't cause a problem. It's a fairly normal situation. Still, that's worth knowing. Thanks for reporting back.

Mikie

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads

 

[sdocker]

Mike,

I meant it was in the report but not on the users system. I would think windows would find a substitute and the worst case would be the report not appearing as expected.

What happened that caused a c00000094 error?

Sam

 

[Mike Lewis]

Sam, that's exactly what I would have expected as well. Perhaps it was as you suggested: something in the font substitition algorithm that caused the error.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads

 

[Olaf Doschke]

I agree it's a case worth knowing. Last year I had a problem with a font, too, it didn't caused a runtime error though.

In general C000:00NN errors are runtime errors and the most famous one is C000:0005 also short C5. Others are very seldom. C% always have to do with some whacky memory addressing error, as can happen if a corrupted dbf or cdx and also scx,frx etc. have pointers to offsets in memo files or internally, that lead to addressing errors. Also objects in memory being addressed after they are released and in a state before garbage collection or anything.

All of them have in common they are so low level, that even the VFP runtime fails and elevates back to the C runtime to handle it. Otherwise you could get a native VFP error number about the error.

As you found out, changing font fixed it, so it was no frx file corruption and the error happened somewhere rather on the OS level between the C runtime and the OS font handling or gdiplus, so it could bee an outdated gdiplus.dll, if you provided one. There were some security fixes about this DLL also concerning VFP and the VFP9 SP2 includes the latest gdiplus.dll, IIRC.

Bye, Olaf.

 

[sdocker]

Olaf,

I don't provide the gdiplus.dll. It is incorporated with the setup created with InstallShield (2012 Spring), so I don't imagine it is outdated.
I am using VFP 9.0 SP2, so gdiplus.dll is probably not the culprit.

Sam

 

[Olaf Doschke]

Yes, it was just one though, everything else applies. You will most probably not find out what the problem was. Maybe even a font file corruption.

Bye, Olaf.

 

[Dan Freeman]

I've also had font substitution crazy behavior, but not crashes.

In the early days of Windows 2000 some installations didn't include Arial, which is VFP's default for new form controls. Imagine my surprise when Windows substituted ...... WINGDINGS. Naturally enough it was during a demo for my then-new boss.