I have an application (COREL PARADOX 8) running in network environment and
my tables forms etc are on Windows NT 4.0 server and users are running
Windows95 OSR2. The problem is that almost EVERY DAY after some hours of
working some of the tables are damaged (index out of date-table needs
repairing and similar messages). After table repairing (Chimney Sweep)
everything is OK, until next time. What can I do?
Many thanks in advance
This sounds like an opportunistic locking problem - try to get your MIS
folks to turn it off.
Here's a list of docs on the subject Paul O'Hagan posted recently:
http://premium.microsoft.com/msdn/library/winresource/dnwin95/d1c/s64b2.htm
http://premium.microsoft.com/msdn/library/officedev/access/bldapps/chapters/ba13_2.htm
http://www.oracle.com/support/bulletins/windows/html/1902.html
http://www2.support.lotus.com/ftp/pub/desktop/Approach/technotes/text/126683.txt
http://www.techexpo.com/bookfair/macmillan/pnwin95.html
http://www.esc4.net/region4/SASI_docs/SA/SASIA3.HTML
- Steve [C-Tech] - please reply to forum