Paradox Tables

[doronlimor]

We have developed a multi user application based on Paradox tables.
All users are connected through the same Net Dir defined in their own BDE configuration.
A code in the program defines the private dir to be C:\Temp
When users browse the database and submit queries, the response time is very fast.
However, when one of the users updates the database the response time of all other users drops significantly,
even when the user who made the updates is disconnected from the database, the session and even after he exits the program completely.
Any ideas how to maintain response time after database updates.

 

[Bystander]

doronlimor,

From what you set out above theoretically there should be no performance issues.

Would you be happy to explain what updating the database entails. Eg is it just adding new rows or updating existing rows? What you have described sounds like a lock is being put on a table but not being released after the change is committed. So a solution might be to read up on locks in the help files and relate this to your database structure.

Locks on tables can be viewed at
Tools - Security - Display Locks

A silly question but one I will ask just in case; is the Net Dir actually on a network shared drive so each person is pathed to exactly the same file by the exact same path in their BDE?

Regards

Bystander

 

[doronlimor]

Thanks Bystander for your reply

1. The updates are simple updates record additions as well as records modifications

2. The NET DIR is on a shared folder in the network
all users are pathed to this folder in their BDE

3. You are referring to Tools - Security - Disply Lock....
where do I find that ?

Thanks again....

 

[TonyMcGuire]

'Based on Paradox tables...'

I hear 'but not using Paradox the Application' in there.

Am I correct?

Tony McGuire
"It's not about having enough time; we have the rest of our lives. It's about priorities.

 

[Bystander]

doronlimor,

You are welcome. I was assuming that you are using the Paradox relational database application so was referring to Tools on the application main menu bar.

I am srabbling about in the dark a bit here but suspect the problems are coming from a write lock on one of the tables. But I could be totally wrong and would need to keep asking lots of questions,which you might easily avoid by seeing if there is a locking issue.

A fair but dated explanation of Paradox table locking is at

http://www.adug.org.au/reference/ti3160.htm

.

I hope that this helps.

Regards

Bystander