![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Chuck, If unload/reload "repairs" your files, then it would seem Btrieve functionality is correct. Surprisingly I might add... For one, Microsoft has equipped XP with a different locking mechanism then they used in 98. You're probably running into numerous locking conflicts when addressing the data from both these versions of Windows at the same time. There are dozens of other incompatibilities, most likely created on purpose in order to lure you into buying more of their products. Or did you manage to get Office 2.0 running on XP as well? AFAIK Microsoft workstation OS's will only allow 10 remote connections to it's shares (including printers). If I read you correct, you say you've got 14 machines trying to connect to a Win98 workstation? Your issues may be related to this machine dropping network connections it considers inactive. sneer> You may want to try to install Linux on that old 33Mhz 486, also from 1991, and use that as a central machine. This should at least solve your networking issues you're bound to have. On 15 Jul 2003 11:41:40 -0700, greg180 (AT) aol (DOT) com (chuck) wrote: Running btrieve 5.10 in a dos window under windows 9x with out problems. 15 machines in a MS network. Files exist on a central machine in a shared directory. This machine is Win98SE. After migration of some of the stations to XP platform we have begun to experience corrupted files. The files themselves still reside on the WIN98se MACHINE. Files are repairable by unload/reload process with no apparent data loss. I suspect the corruption is in indexes. Corruption has occurred intermittently on 3 of the six files. Any help in diagnostic techniques, fault isolation or other input would be more than welcome. Chuck Gordon Bos Q-RY Solutions +31-(0)15-2564035 http://www.q-ry.nl/ |
![]() |
| Thread Tools | |
| Display Modes | |
| |