Sage 100

MAS90 4.3 Client trying to print 500 statements, at the end of preview, they receive the following message: ""Unable to view statement printing report. Query Engine error: ""S0000:{Providex}{ODBC Driver}{PVKIO} Unable to read Key data block."" cannot find any variation of this on Knowledge base. They receive the same message when printing straight to printer. tried different printers. tough to troubleshoot because it takes 8 hours to run the crystal run time before anything happens. I thought it might be an invalid date, but I cannot find one. They have 106,000 Invoices in history. Has anybody else seen this? thanks! Michael

8 hours? Are you serious? What if you run on the server? Has it always taken this long? 106K in invoice history or in the open invoice table? Did it work ok last month? Has the statement been modified?

This is a data corruption error. Rebuild Key Files on AR_TransactionPaymentHistory (AR6) and AR_OpenInvoice (AR4) at least.

Worked last month. I have not tried to run at the server. I looked at both of those files and nothing jumped out. I also looked at AR_OpneInvoice. How do I go about finding the dates. I used crystal and unchecked the Null Dates in ODBC. All of the dates looked fine.

All else fails - does generic form work?

Generic form works for one customer, and other random customers.

I think you want to have the Null date selected in ODBC options. @RobertWood had a nice post about this. https://90minds-com.socialcast.com/messages/13536751

Another post i read said uncheck the Null Date, which was already unchecked. Robert says to check the Null Date. I will try that.

I think Alnoor wrote the original post that I was quoting.

My experience is that if it's a date issue and you don't use the null date option that you will error out if you are viewing the date field which contains the bad date.

How about dumping the statement work file to Excel to see what (doesn't) appears?

Tried the null Date in OBDC on and off. Neither returned any kind of error. Tried dumping all tables into excel. Everything looked fine there also. Printed statements from A-K successfully. Now printing L - Z. Hoping we get it there. but then we will have to split the list in half until we find the right customer. that will give us a start. What a long and boring and expensive process.

Did you look at dates in the AR_TransactionPaymentHistory file as well? Is this a customized statement? Why oh why would it take 8 hours to run? Did you try previewing the generic form for all customers to see if it works?

T did try the AR_transaction History file. I don't know why it takes so long. This is actually not my client. I was running support while their consultant was in Hawaii. Did not try generic statement on all customers because it takes so long to run. We wanted to get at least some statements out the door.

Did you try the rebuilds as Alnoor suggested?