Odd error message
Nancy Palmquist
nlp at vss3.com
Tue Aug 17 12:40:15 PDT 2010
Richard,
It makes perfect sense that Windows would crash when it had "No Error"
I have fought with form printing from clerk also. In my case, the first
output of the form seems to disappear - nothing prints. A second
attempt seems to make it work and then it works fine after that.
Something about opening and closing the print buffer. I did all my
printing with programming, not the general F command. Less control there.
I got it pretty close to full functioning. I think the only way to make
it perfect is to write to a file and then print it from windows. Like
the RTF thing works.
Nancy
On 8/17/2010 1:45 PM, Richard Kreiss wrote:
> One of my client's received the following when attempting to print an
> output:
>
> This error occurred on the first attempt to print this output using @keyF
> and selecting the proper letter from a listbox and then form xxxxxx to print
> the letter.
>
> Upon return to the record, pressing F again prints the letter. Move to a
> new record, the same thing happens.
>
> Any ideas why this should just start happening?
>
> *** A System Error Has Occurred ***
> : No error
>
>
>
>
>
>
>
> Exception error -1073741819 in process failed 0(0x00000000)
> compel="(null)"
> command="C:\fptemp\$$FP007a.bat
> "
> Press Enter:
>
>
>
>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>
--
Nancy Palmquist MOS& filePro Training Available
Virtual Software Systems Web Based Training and Consulting
PHONE: (412) 835-9417 Web site: http://www.vss3.com
More information about the Filepro-list
mailing list