>>The situation is this:
>>
>>Our hospital system was formerly pure Fox 2.6 developed. It runs smoothly and no problem at all. Recently, we developed some modules in VFP 5.0 accessing Fox 2.6 tables (Free tables only) and there, the problem started. Within two weeks of implementation, one of the table approximately 4 Million records in size was corrupted 3 times at the minimum. This is not happening until the VFP modules were implemented.
>>
>>My suspicion is that, there should be a size limitation of Fox 2.6 table. It might also be the integration of VFP modules. What do you think?
>>
>>TIA
>
>Hi Jess,
>I'm running dual access to over 700MB of data files from both VFP6, 5, 3 and FPW2.6
>No corruption problems what-so-ever. (Using NT4 servers)
>So I'm afraid that's no help.
>Has the transaction volume gone up since?
Gone up as usual (few thousands per 24 basis), only that some modules were converted into VFP.
>Have users got new client software like Novell 32 bit client or the old MS client, which can be dogs, depending on the verions?
We are beginning to think that it is the Novell 3.11 that causes the problem.
We have actually a POS system which have the same setup: Cashiering was done in Fox 2.6 and its Back-End modules were done in VFP, but we never encounter such a problem.
JESS S. BANAGA
Project Leader - SDD division
...shifting from VFP to C#.Net
CHARISMA simply means: "Be more concerned about making others feel good about themselves than you are in making them feel good about you."