Board index » delphi » HELP - GPF after close.

HELP - GPF after close.

I'm trying to write a mail label printing program which was created using
Delphi 1.x (16bit).  It extracts information from a Paradox table and prints
mailing labels.  The part which gives me trouble is changing fonts
from Times New Roman to Postal Barcode and back again.  After much sweat
and cribbing from some excellent shareware (EDSPRINT) I seemed to get it
working for my dot matrix.  Then I tried my laser (IBM 4019).  The program
appears to run to completion (I've single stepped through with many Watches)
but after close I get a general protection fault.  My link edit map shows me
that this exception is somewhere far into the code for FORMS.

I am running under WINOS/2 because I'm an OS/2 user.  I then took the
code to a bare DOS machine and got the same results except that Windows 3.1
also gave me a modal message block saying something illegal had been done
with fonts before it took the exception.

I don't expect anyone to give me a solution but I'm looking for straws to clutch
at; what sort of things might one do which makes Borland's FORMS code
go haywire after an appatently normal completion?

Any help would be appreciated.

 

Re:HELP - GPF after close.


How did you change fonts ? I ask because I had similar problems changing
brush colors.

In article <33f789a...@news1.ibm.net>, tmsp...@ibm.net writes

Quote
>I'm trying to write a mail label printing program which was created using
>Delphi 1.x (16bit).  It extracts information from a Paradox table and prints
>mailing labels.  The part which gives me trouble is changing fonts
>from Times New Roman to Postal Barcode and back again.  After much sweat
>and cribbing from some excellent shareware (EDSPRINT) I seemed to get it
>working for my dot matrix.  Then I tried my laser (IBM 4019).  The program
>appears to run to completion (I've single stepped through with many Watches)
>but after close I get a general protection fault.  My link edit map shows me
>that this exception is somewhere far into the code for FORMS.

>I am running under WINOS/2 because I'm an OS/2 user.  I then took the
>code to a bare DOS machine and got the same results except that Windows 3.1
>also gave me a modal message block saying something illegal had been done
>with fonts before it took the exception.

>I don't expect anyone to give me a solution but I'm looking for straws to clutch
>at; what sort of things might one do which makes Borland's FORMS code
>go haywire after an appatently normal completion?

>Any help would be appreciated.

Kind Regards
Claire

Other Threads