How to guarantee minimum problems with corrupted tables in Paradox?
Bill Todd
http://community.borland.com/article/0,1410,15209,00.html
On Tue, 10 Sep 2002 19:23:35 +0200, "Jaroslav Marko" <ja...@ivaso.sk>
wrote:
>Hello,
>
>I just want to be sure, that I know everything what I can about making
>Paradox tables "corrupt secure" enough in network usage.
>
>Using D5.
>
>- BDE alias set to network path
>- Net Dir on server with all access rights for all users (and set the same
>for all users)
>- Local Share in BDE setting - true
>- in TTable component should be set the Session
>
>Problems which I had:
>- corrupted tables after several days of usage in 5 users network (HW and
>LAN 100% ok, win 2000 and 98)
>- from time to time error message -> Lock file has grown too large
>- Very often BLOB fields corruption
>
>Questions:
>- How does it work when there is already some other Paradox network software
>on same hardware? (can I use same netdir etc? (I think no)
>- How can I do some prevention? (deleting LCK files?... Checking tables by
>opening?)
>
>Can you give me some more advices and opinions, please.
>
>Thank you in advance.
>Jaro
>
>
--
Bill (TeamB)
(TeamB cannot respond to questions received via email)