Welcome, Guest. Please Login.
05/14/25 at 13:11:38
News:
Home Help Search Login


Pages: 1
Send Topic Print
Fatal Error when printing Statements (Read 474 times)
gtladmin
Active Member
*****


Diving is fun,
diving is fun!

Posts: 1306
Gender: female
Fatal Error when printing Statements
07/28/06 at 13:24:57
 
In AR, our receivables person was printing all the statements.  It got to one particular customer record and a window popped up that was titled "FATAL ERR - File t6ARE.SRC LIne: ....." (that's all you could see).  You could only click on the OK button.  It would bounce out of the printing.  
 
I had her skip that record, and all the other statements printed just fine, so it would appear there's some sort of issue with that one customer record. So you do repair one
record?  Do you have to just reindex the bkarcust file?
 
TIA,
 
Val
Back to top
 
 

Val Feehan
  IP Logged
NovaZyg
Administrator
*****


When all else
fails.. Read the
instructions.

Posts: 789
Gender: male
Re: Fatal Error when printing Statements
Reply #1 - 08/01/06 at 03:53:26
 
Val,
 
 Sounds like that Customer has an Invoice or voucher with a terms number that is outside of the range. Valid terms numbers are from 1 - 20. We have seen this happen before. Use MaintainDatabase and open bkarinvt and sort by customer. Then look for the bkar.invt.termn that is outside of the range.  Its not easy to spot simetimes, so good luck.
 
Back to top
 
 

Allen Landry
Evo~ERP

EvoERP and DBA Classic always Beta's of the Latest versions.

WWW   IP Logged
gtladmin
Active Member
*****


Diving is fun,
diving is fun!

Posts: 1306
Gender: female
Re: Fatal Error when printing Statements
Reply #2 - 08/01/06 at 05:13:39
 
Hi Allen,
 
Very good, I'll give that a try.  Thank you so much!
 
Val
Back to top
 
 

Val Feehan
  IP Logged
dameng
Senior Member
****


DBA / EVO Software
Consultant

Posts: 275
Gender: male
Re: Fatal Error when printing Statements
Reply #3 - 08/08/06 at 14:34:47
 
if you have an ODBC connection set up, you can run the following SQL statement:
 
SELECT * FROM BKARINVT
WHERE BKAR_INVT_TERMN > 20
 
that will show you the errant records. you can edit the faulty value right there, (type in the new value and then move the cursor up or down to evoke the change)
 
hth
Back to top
 
 

Dave Mengelkamp
Digital Consulting
760.832.2536
davemeng@earthlink.net
Email WWW   IP Logged
Pages: 1
Send Topic Print