ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Manufacturing >> I CANNOT CLOSE MY W/O
http://www.istechforum.com/YaBB.pl?num=1051891171

Message started by mwee on 05/02/03 at 09:59:31

Title: I CANNOT CLOSE MY W/O
Post by mwee on 05/02/03 at 09:59:31

HI
I CANNOT CLOSE MY W/O, BECAUSE RECORD LOCK. WHAT SOULD I DO ? HELP ME PLEASE
THANKS FOR EVERY ONE
MICHAEL

Title: Re: I CANNOT CLOSE MY W/O
Post by fredh on 05/02/03 at 11:11:00

If you don't want to just wait...

Write down the name of the file that's locked and go into the Pervasive Monitor.
(If you do this at the server you won't have to do an administrator login .)

If you're not at the server select Options - Connect and login as an administrator.

Select Microkernel - Active Files

Select the locked file's name (watch your extensions).
A list of users who have the file open will be displayed on the right.

Select each user until you find the one who's Record Lock Type: says Single. That's the person you'll have to contact about finishing up their work.

Title: Re: I CANNOT CLOSE MY W/O
Post by aricon on 05/02/03 at 22:59:56

Very good Fred! I wasn't aware of anyone that had figured that out... ;)

Title: Re: I CANNOT CLOSE MY W/O
Post by fredh on 05/05/03 at 05:48:59

One of the many advantages of working with a consultant. :)

Title: Re: I CANNOT CLOSE MY W/O
Post by aricon on 05/05/03 at 09:00:21

Finally! Someone that points out that there are some REAL advantages to having a professional help them, even though there is a cost to it! ;D

Title: Re: I CANNOT CLOSE MY W/O
Post by kerric on 05/06/03 at 07:14:28

I had to add to that commentary regarding consultants.

When our company purchased DBA we began using a consultant. Here we are one year later and still struggling to understand how the program works.

I agree, a GOOD consultant is extremely beneficial with DBA. The consultant we were referred to had the knowledge, but the ability to share that knowledge with beginners is the skill needed. It's no good locked up in a brain-shaped vault.

Title: Re: I CANNOT CLOSE MY W/O
Post by Tanja on 06/10/03 at 12:55:22

kerric wrote: Here we are one year later and still struggling to understand how the program works.

I agree, a GOOD consultant is extremely beneficial with DBA. The consultant we were referred to had the knowledge, but the ability to share that knowledge with beginners is the skill needed. It's no good locked up in a brain-shaped vault. must

I have to agree! Speaking with consultants is even more difficult than learning a new language

Title: Re: I CANNOT CLOSE MY W/O
Post by aricon on 06/11/03 at 00:23:21

Tanja,

Are you referring to me?

Title: Re: I CANNOT CLOSE MY W/O
Post by fredh on 06/11/03 at 07:37:00

I guess we found a gem:

Sue Scipioni, DBA Consultant; North Beach, MD SUESCIPIONI@cs.com

^{Copied from the Consultant List at http://www.istechsupport.com/consultant_list.asp}

Title: Re: I CANNOT CLOSE MY W/O
Post by fhcinc on 08/21/03 at 14:31:54

My question is why is this record locking happening? I have been doing this task for over a month. I get over
50 a day!!! All different modules and files. (The WO???? and BK???? files are the most frequent)

Brian

Title: Re: I CANNOT CLOSE MY W/O
Post by aricon on 08/21/03 at 18:09:30

Record locking in DBA is due to the basic design philosophy. DBA is a transactional database management system, not a true RDBMS (relational database management system).

Therefore, all of the mechanisms contained in Pervasive to manage file and record access and challenges (rules based "who-wins" programming for multiple file/record requests), is utterly useless.

Many record locks had to be purposefully programmed in to the run files to try to ensure some reasonable data integrity.

Additionally, you will sometimes get them even when they were not specifically programmed. This is due to a good portion of the underlying file structure that DBA was created on for some of the major system files.

Simply put, they were BADLY designed. If you have no more than 5-7 users max, and no more than 1 user that uses most of a certain range of files (i.e. 1 person entering Sales Orders, rather than 2 or 3), then you should experience a pretty small occurrence.

Also, some basic database maintenance needs to be done on a regualr basis to help alleviate some of the symptoms.

Would you expect to run one of the machines in your shop for a long time without any preventative maintenance? Well, Pervasive/DBA is the same.

You should also do regular system maintenance on your server and your workstations. This is a MUST for proper performance no matter what applications you are running.

Most companies however, have no clue about running regular maintenance on the computer hardware/software, but they want it to always work flawlessly. Not a very reasonable expectation.