We have one customer who is getting a printer abort while printing a text file. We upgraded them to a new version from 1.9 331 to 1.9 355. They have the same printer as they did using 1.9 331. This part of our code has not changed at all and I and lots of others have no problems printing text files.
Could this be a printer driver issue?
Operating System is Windows XP
Toshiba - eStudio 351c (photocopier/printer)
Same Printer as last year
Date : 09/09/10
Time : 08:23:42
Procedure : DC_PRINTER:ATSAY
Line Number : 2335
Information : Error BASE/5
Description : Internal data structures corrupted
Operation : graStringAt
Thread ID : 1
Source :
Called from : (B)INIT: _DCINIT(28)
Called from : DC_PRINTER:ATSAY(2335)
Called from : DC_PRINTFILE(3897)
Called from : WDSEOPN(533)
Called from : XWDSE(37)
Called from : UTILMAIN(282)
Called from : XUTIL(34)
Called from : LMAIN(1786)
Called from : MAIN(1815)
Please Help - Abort DC_PRINTER:ATSAY
Please Help - Abort DC_PRINTER:ATSAY
Last edited by Jeanne on Wed Sep 29, 2010 1:31 pm, edited 1 time in total.
Re: Abort DC_PRINTER:ATSAY
did you "verify" Version after "Patch" ?Jeanne wrote:We upgraded them to a new version from 1.9 331 to 1.9 355. They have the same printer as they did using 1.9 331.
use XppLoad from your Application Path to "see" which DLL will be load, perhaps you have somewhere older Xbase++ DLL ?
greetings by OHR
Jimmy
Jimmy
Re: Abort DC_PRINTER:ATSAY
Hi, Jeanne.
Did you rebuild your eXpress++ with the new Xbase version?
Did you rebuild your eXpress++ with the new Xbase version?
Best regards,
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Re: Abort DC_PRINTER:ATSAY
Yesterday I sent XppLoad to our tech support who is handling this. The school seems to have been closed yesterday because no one answered. Yes we did rebuild eXpress with xBase.
Jeanne
Jeanne
Last edited by Jeanne on Tue Sep 14, 2010 6:41 am, edited 1 time in total.
Re: Abort DC_PRINTER:ATSAY
I ran xppload on my system and had these two files that did not look correct. I am wondering why these show up as 311 and if that is ok.
C:\Program Files\ALASKA\XBTW32\LIB\XbtBase1.dllVersion: 1.90.331
C:\Program Files\ALASKA\XBTW32\LIB\XBTBase2.dllVersion: 1.90.331
C:\Program Files\ALASKA\XBTW32\LIB\XbtBase1.dllVersion: 1.90.331
C:\Program Files\ALASKA\XBTW32\LIB\XBTBase2.dllVersion: 1.90.331
Re: Abort DC_PRINTER:ATSAY
Hi, Jeanne.
These are the Xbase-tools-DLLs. The version # is correct, since there was no update for the tools.
These are the Xbase-tools-DLLs. The version # is correct, since there was no update for the tools.
Best regards,
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Re: Abort DC_PRINTER:ATSAY
Is there a way to test the eXpress DLLs version?
Re: Abort DC_PRINTER:ATSAY
Yes, try:Jeanne wrote:Is there a way to test the eXpress DLLs version?
dc_VersionExpress(0)
and
dc_VersionExpress(3)
Regan Cawkwell
Real Business Applications Ltd
http://www.rbauk.com
Real Business Applications Ltd
http://www.rbauk.com
Re: Abort DC_PRINTER:ATSAY
Call DC_Dot (Alt-D) and type:
Code: Select all
? DC_VersionExpress(0) // full version
? DC_VersionExpress(3) // build number
Best regards,
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Re: Abort DC_PRINTER:ATSAY
I was looking for an app that a customer could run that might tell me what eXpress DLLs versions that they had on their system.Call DC_Dot (Alt-D) and type:
Code: Select all
? DC_VersionExpress(0) // full version
? DC_VersionExpress(3) // build number
Jeanne