aricon
Active Member
   

Systems Consulting-See website for products!
Posts: 1283
Gender:
|
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.
|