WoodyJ3
asked on
Paradox Problem
Hi guys,
I'm using a paradox database with multiple users over a network (bad idea I know, wasn't my idea but I'm stuck with it).
Apparently a user is getting a message that says "too many locked records" what does this mean? whys it happening?and it there anyway of stopping it????
I must say that paradox is by far the worst database ever!!!!
Please help.
thanks
woody.
I'm using a paradox database with multiple users over a network (bad idea I know, wasn't my idea but I'm stuck with it).
Apparently a user is getting a message that says "too many locked records" what does this mean? whys it happening?and it there anyway of stopping it????
I must say that paradox is by far the worst database ever!!!!
Please help.
thanks
woody.
listening....
The most probable cause of this (I have found) is that you haven't set the sessions private directory to somewhere on the local computer.
For example
session.privatedir := 'c:\temp';
That will ease the locked record problem. You can also test out your app with localShare = False (BDE Setting).
If these dont solve your problem then it may be caused by a genuine locking problem. Are you applying read locks to records? Are you freeing TTables without closing them?
For example
session.privatedir := 'c:\temp';
That will ease the locked record problem. You can also test out your app with localShare = False (BDE Setting).
If these dont solve your problem then it may be caused by a genuine locking problem. Are you applying read locks to records? Are you freeing TTables without closing them?
listening...
ASKER
The steps I use are
run two queries.
append record to a table.
close both queries.
Open both queries. (refresh unreliable)
If you do this enough times you get the error.
This error only seems to happen when I connect to a database that is a share on another computer.
I'll try out that local share stuff.
Thanks
Woody.
run two queries.
append record to a table.
close both queries.
Open both queries. (refresh unreliable)
If you do this enough times you get the error.
This error only seems to happen when I connect to a database that is a share on another computer.
I'll try out that local share stuff.
Thanks
Woody.
ASKER
nah, tried that. Didn't seem to make any difference. I just wish I had time to convert the lot to a decent database.
Woody.
Woody.
hi WoodyJ3,
i would not say that paradox is worst.
two tips
don't use cachedUpdates, if you are modifying a large amount of records in one step.
open the table exclusive.
you cannot lock more than 512 records at one time (or was it 1024?)
meikl
i would not say that paradox is worst.
two tips
don't use cachedUpdates, if you are modifying a large amount of records in one step.
open the table exclusive.
you cannot lock more than 512 records at one time (or was it 1024?)
meikl
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi Woody,
I think that is happening because your tables and net dir file are at the same folder.
The solution I propose is make a sub-folder "data" and put all your tables there, and another sub-folder "netdir" and put the netdir file there.
Also, on all workstations change DBE configuration NET DIR='net_path\netdir'.
Isak
Listening.....
ASKER
Im not using cached updates and my Net file is in the root of the share, with the data a folder below.
The comment made by Portal is interesting though. I'll check that one out.
I'm getting the feeling that Paradox was invented solely to p**s me off.
I'll let you all know.
Cheers
Woody.
The comment made by Portal is interesting though. I'll check that one out.
I'm getting the feeling that Paradox was invented solely to p**s me off.
I'll let you all know.
Cheers
Woody.
ASKER
err... well... I'm still investigating the problem with no luck so far. I've still got a few possible ideas to fix it so I'll let you all know sometime during the week.
ta
Woody.
ta
Woody.
ASKER
Comment accepted as answer
ASKER
I tried it and it doesn't crop up as much as it used to so it's a bit better.
I've had enough of the bloody crap database so I'm half way through upgrading to SQL.
Many Thanks
Woody.
I've had enough of the bloody crap database so I'm half way through upgrading to SQL.
Many Thanks
Woody.