Data 'crossover'

[gothbabe55]

Hi - I am hoping someone might have some suggestions on this, or maybe even identify a cause. We have an application that we write using Foxpro. The problem is that we have a user who is encountering 'crossed over' data - ie. they are viewing the records of a .dbf file which is located in another directory. The paths in question would be similar to the following:

C:\dirA\dirB\demo.dbf
C:\dirA\dirC\demo.dbf

where someone is working in the demo.dbf in dirB and suddenly encounters/writes data to dirC.

I know that this sort of issue has been experienced where the data is housed on a server where per server licencing is in use and there are not enough licences to logged on users - hence 'pinched' sessions between users. This is *not* the case however - licencing is all good. Does anybody have any ideas or suggestions on this?

 

[Mike Gagnon]

gothbabe55

Is it possible that these tables are in the dataenvironment of a form, where they would automatically get opened?

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[gothbabe55]

Hi Mike

No, we are not using the dataenviroment of the form - we manually open and close all tables.

 

[Mike Gagnon]

No, we are not using the dataenviroment of the form - we manually open and close all tables.

Then something is switching your SET DEFAULT. Reset it before opening your data.

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[gothbabe55]

Hi Mike

Thanks for your responses on my post June 10/11. FYI: it *appears* that possibly Netshield anti-virus software is causing this when it is set to scan the directory for our software. I am currently communicating with Network Associates regarding this, unfortunately the client who has been experiencing the difficulty and is meant to be testing the suggested fixes from NA is not exactly being co-operative, but since they have turned off the scanning on the directory, the problem doesn't seem to have occurred again. I will keep you posted if I hear anything further on this.

Cheers
Amanda (gothbabe55)