---

bbowie wrote:

I am trying to print bills and received error messages.  The messages said to run the data verification report.  The report found 3 errors as follows: 

 

Checking Integrity Change Log

ERROR

The Paradox table appears corrupted

Number of records found (9009) does not match number of header records (9010)

 

Linking Extended Funds

ERROR

Link to Funds Transaction incorrect. Expected record ID 135

ERROR

Link to Funds Transaction incorrect. Expected record ID 136

Table Error Total: 2

 

How severe are these errors & is it ok to repair them?  If so, which repair do I do since there are 3 choices: Rebuild data indices, validation errors or integrity errors.

 

Any help you could give would be appreciated since our billing is at a stand still right now.

 

 

---

Okay, let's try something fairly benign before we break out the big guns.

1.  Make a backup.  If you don't and you do anything else, it may make it worse and there will be no fall back position.  Then make another one and take it OFF the machine you are working on.  Put in on a CD ROM, thumb/flash drive, whatever, but get it off the machine.

2.  Run a Data Verification and tell it to Rebuild Data Indexes ONLY.  Wait (it could take a while).  See what the report says at the end.

3.  Run a Data Verification again with ONLY Look for Errors checked.  Does it come back clean?

Let us know.

Nancy Duhon, Esq.

Certified Consultant for Timeslips and Amicus Attorney

Atlanta, GA 

www.duhon.biz

[email protected]

404-325-9779 

P.S.  If you think this suggestion was especially helpful, please consider clicking the KUDOS! (yellow) icon in this message.  Thanks. 

Hi Nancy,

Are you going to be able to help me?  I am really desperate now.

Barb

The pdox and paradox files you mentioned are temporary files that should not exist if Timeslips is closed, unless you have some other BDE application running like Goldmine or Word Perfect. If none of these are running please delete the files.One other thing you should do is remove temp files from the machine that you are using for data verification. This can most easily be done by going to start - all programs - accessories - system tools - disk cleanup.

When you run data verification are you running it across the network or directly on the same computer as the database. It is always better to run on the computer with the database or to bring a copy of the database local to do data verification. 

Assuming you have removed all the pdox and paradox files please then try to run data verification on a local copy of the database. If you still get the linking fund errors at that point make a backup and try the reindex again. If you are still getting the error you can try running data verification with attempt to repair validation errors checked. Let us know what happens. If you are in a hurry for this to be repaired or are not completely comfortable with the instructions please contact a Timeslips certified consultant for assistance. And remember, before you do anything, MAKE A BACKUP.

I tried to delete the pdox & paradox files in the Timeslips directory but it kept telling me that they were in use even though no programs were open on my computer and no one else had the program open.  I did find some of them in a "Road" program we use and I renamed them old. I removed all the temp files from the machine.  I ran the data verification and still got the 2 linking funds errors so then I ran it and repaired the validation errors.  It found those 2 errors (Record ID 135 & 136) and gave the error message: part of the record is missing and without the data, it is useless and has been deleted.

I then went back into the program and tried to do a bill.  Now I get this error message:

Address Violation Error

Area: System Error

Code: 2

Address: Exception t System Exception C in module Timeslip.exe at 002AD264

When I clicked ok it then gave me an "Error handler message failed"

Hopefully you can help me again.

Signed,

At My Wit's End 

Code 2 errors are usually caused by system resources. You can try rebooting the computer and see if that helps. You might also need to change your BDE settings, primarily max file handles. I would also clean out all temp files.

The fact that validation says it deleted a record means you must go through your reports carefully to make sure that no harm was done. At a minimum run your aged AR and aged WIP reports.

Hi Caren,

Well I had no luck with the BDE settings, however, my problem is solved.  I ended up restoring a backup up from last week.  Then I somehow came to the conclusion that maybe the last client record we entered might be bad.  So I made that client record inactive, transferred all the slips to the new client record and, printed the bill.  Hallelujah!!!  I know this is not the end to my problems because we do get a lot of error messages but at least for now we can move forward.  Thanks for staying with me on this issue, I appreciate it.

Barb

Go to control panel and open BDE administrator. Go to configuration - system - init. What is maxfilehandles set to? If less than 200 please change it to 200.

If still not working properly you might want to completely uninstall BDE -- see instructions in the knowledge base. Then delete all temp files - I like start - programs -  accessores - system tools - disk cleanup. Reboot teh computer and then reinstall BDE. After you reinstall BDE go back into the administrator and change maxfilehandles as described above.