When running a report on interactive Paradox and I choose to print
the report with (File+print) or (Ctrl + P) a dialog pops up where I
can select a printer, pages to print, etc.; if I press the <close> button
Paradox hangs, the same with Runtime.

Is there a patch or SP or workaround to this problem ?

I think that I never noticed this before cause I always choosed to <Print>
but this time I had to cancel the printout, pressed the <close> button and
was surprised.

I tried to figure out & couldn´t so I did an uninstall-reinstall + SPs
and seeing that nothing changed, I reinstalled Windows + Pdox+SPs
with still no change.

Win XP Pro SP2 - Pdox10 + SP3

Thanks
Anthony

Anthony,
See answer in group.
Jostein Bakke


"MA" <a@a.com> skrev i melding news:44b542a8$1 (AT) pnews (DOT) thedbcommunity.com...

Anthony,
it's probably the ctfmon.exe process that's causing it. Try aborting it,
and see if the problem stills exist.

BTW: You can tell Windows to stop executing ctfmon.exe permanently, but I
can't remember how.... As far as I remember: You have to UN-check some
"Enable advanced eastern language...something" in the Windows control panel
somewhere. Perhaps you can find it, or you could try searching the web.

Jostein Bakke


"MA" <a@a.com> skrev i melding news:44b542a8$1 (AT) pnews (DOT) thedbcommunity.com...

Information on how to remove ctfmon can be found at my site, URL in my
tagline. Look in the document Errors explained. Search the index for
"Paradox stops responding."

--
Bertil Isberg - CTECH
Paradox buglist:
online: http://hem.bredband.net/bertilisberg/

"Jostein Bakke" <bakkeb (AT) online (DOT) no> skrev i meddelandet
news:44b6a89f (AT) pnews (DOT) thedbcommunity.com...

I´ll have a shot at that and report back.

What about rolling my own print dialog and using the record types
(PrinterOptionInfo
and ReportPrintInfo) ?
Do you know of any issues regarding the two ?
Which offers garanteed results and less errors?

Anthony

That is what I have done to avoid this problemwith CTFMON.

I use the ReportPrintInfo with the dynamic array syntax.

Anders

I have no answer on this question.

--
Bertil Isberg - CTECH
Paradox buglist:
online: http://hem.bredband.net/bertilisberg/

"MA" <a@a.com> skrev i meddelandet news:44b71243 (AT) pnews (DOT) thedbcommunity.com...

That is what I have done to avoid this problemwith CTFMON.

I use the ReportPrintInfo with the dynamic array syntax.

Anders

Ok, sorry for the long delay but had to be out at some clients & you all
know
how it is...

CTFMON.exe was the cause and Paradox speeds up a lot more when it´s
disabled.

I decided to roll my own print-dialog.fsl and to use the ReportPrintInfo
dynArray syntax
as Anders mentioned & the results are fine...

I prefered doing it this way cause a client can suddenly appear with the
need of having
ctfmon.exe enabled & the problem pops up again.

Thanks to you all out there,
Anthony


"Anders Jonsson" <gt3TakeThisAway (AT) bredband (DOT) net> escribió en el mensaje
news:44bbfc7d (AT) pnews (DOT) thedbcommunity.com...