ISTech Support Forum - BTRIEVE error

Welcome, Guest. Please Login.

	05/10/25 at 21:32:55 News: \| IS Tech Support \| Evo~ERP \| Evo Wiki \| Forum \|

ISTech Support Forum › Evo-ERP and DBA Classic › Problem Reports - Sporadic

‹ Previous topic | Next topic ›

Pages: 1

BTRIEVE error - P/01/BKDCTLAB.B01-84 (Read 931 times)

GP50

Browser

I love YaBB 1G -
SP1!

Posts: 20

BTRIEVE error - P/01/BKDCTLAB.B01-84
05/13/08 at 07:31:34

I am using DBA Manufacturing for Version 2004.1 with IS Tech Support 12/15/07. I am getting the error I listing in the Subject and my employee can not log off their labor from the work order. He is using EVO but this happen to the another person and she was not using EVO and it was a diffrent work order. Right now when the person attempts to log off they are logged off 15 to 20 times and logged back on 15 to 20 times all in one action by the computer.

Thanks in advance for the help.

IP Logged

kkmfg

Senior Member

Ghost of the code

Posts: 375
Gender: male

Re: BTRIEVE error - P/01/BKDCTLAB.B01-84
Reply #1 - 05/13/08 at 07:48:44

That error code indicates that the record which is trying to be updated is already locked. This is probably due to a program error/crash.

A record can be locked when it is being updated to keep other users from also changing it and causing chaos. But it should be unlocked once the user is done editing it. It seems that this has not properly happened for you. The easiest way to unlock a record is to reboot the database server. But you should be sure that everyone is off the system first.

Collin
K & K Manufacturing, Inc

EvoERP Version 1-22-10 SP3
5 User Workgroup Pervasive 10

IP Logged

GP50 Browser I love YaBB 1G - SP1! Posts: 20	Re: BTRIEVE error - P/01/BKDCTLAB.B01-84 Reply #2 - 05/14/08 at 06:13:37 I tried this suggestion last night and I'm still having the same error. thanks for he help.
Back to top	IP Logged

kkmfg Senior Member Ghost of the code Posts: 375 Gender:	Re: BTRIEVE error - P/01/BKDCTLAB.B01-84 Reply #3 - 05/14/08 at 09:31:33 Hmmm... That's fun. I don't know why the record would still be locked after you reboot. Maybe PervasiveSQL keeps the lock status in some sort of file. I'll try to look this up. In the meantime, I hope someone else can give you a suggestion that works.
Back to top	Collin K & K Manufacturing, Inc EvoERP Version 1-22-10 SP3 5 User Workgroup Pervasive 10 IP Logged

Pages: 1

ISTech Support Forum › Evo-ERP and DBA Classic › Problem Reports - Sporadic

‹ Previous topic | Next topic ›