Identify Bad Key in v6.15 and how to repair

[Julio44]

Currently using Btrieve 6.15 on a novell 4.1x server as the backend for a QuickBasic application.

I know very little about any of this as it was developed by a vendor.


Have an issue with one option in the application. Btrieve is returning the following error while trying to access the data:

0040680010930100R1000A906221356 [Enter] to continue btrv err #-1 OP # 10 file # 3 Key # 2 0040680010930100

I assume the character combos at the beginning and end have to do with the data (id/location possibly) that is being (trying to be) accessed.

I have done a *butil -Save* and *butil - recover* on the file with the hopes it would repair the key with no success. I got this info from the vendor but he is in bad shape and has little knowledge to share.

Can anyone provide any insight on how to identify and/or correct a bad key or any other info that may be helpful. Kind of desperate at this point. Only other option would be to replace the data files with some that are about 3 weeks old and see if this corrects the issue at the risk of losing some data (obviously).

 

[mirtheil]

The error you list is not specifically a Btrieve error. The "btrv err #-1" is strange because there's no -1 error code. All Btrieve errors are positive numbers. Here's a link to all of them:

http://www.pervasive.com/library/docs/psql/950/code_msg/index.html

The "OP # 10" is a Btrieve operation. The 10 operation is a Get Less Than operation. If it's failing, it might be a programming error in the application.
If you've got the Btrieve utilities, you could try to replicate the behavior in the application to get the real error. You'd want to Open the data file in the Function Executor, then issue a Get Less Than using the same key number and key value (probably those values in the error).

Since BUTIL didn't help, there may not be anything wrong with the data file. It may be something else. I remember one issue with Btrieve and Novell 4.x where the OS Turbo Cache would become corrupt and erroneously report a status 2 (file corruption). There were several fixes for this from Novell.

Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician

http://www.mirtheil.com

 

[Julio44]

Thank you.

And now for another question.

Should I really be looking at the code if it hasn't been modified in over 2 years? The app has been extremely stable and from the little experience I have with it, the errors have been data related. I also noticed I couldn't find a '-1' error.

Also, this app interfaces with various pieces of lab equipment. This issue only occurs with one of the machines/machine data. All the other data/interfaces don't seem to be suffering this issue.

I also read a bit about the turbo cache issue but didn't look into it to much. I guess I'll start reading up on that.
Do you have any other suggestions/ideas?

thanks again...

 

[mirtheil]

You're right, code that hasn't been touched probably isn't the issue. If it's only one machine, there might be something about that machine that's causing it. Perhaps a network issue of some sort. How often does the error occur and does it occur in some pattern (same time of day, under heavy load, first thing in the morning, etc)?


Mirtheil
Certified Pervasive Developer
Certified Pervasive Technician

http://www.mirtheil.com

 

[Julio44]

There's no specific time. The issue is as follows:

We have a pc connected via serial port to a piece of lab equipment (Cell Dyne 3700). The app runs two instances, one serves as the "receiver" and when the data is sent from the lab machine, the "receiver" instance catches the data and I believe it stores it in the btrieve result file.

The second instance allows you to select a result(imported data) and view the data that was imported (received). Here is where the problem is. When trying to look at the data, the app is showing a blank screen rather than a data edit screen. No error is given at this point. If you use a different option to pull up a cumulative result which will show all the data for account on a given date. This is where the above mentioned error occurs.

I also believe this is a data issue of some type because even the older dates which were completed won't display the data for this particular type of result.

Hope this isn't more confusing. I can give a more detailed explanation if necessary.

thanks again..