Ria,

Is it possible that the server on which the tables reside is getting busy with other work around the time that allthe funny stuff happens? Especially heavy print activity?
Long ago here a problem was described where strange things would happen in an application and that person found that it always coincided with heavy printing from the serve and eliminating all print activity eliminated the problem.

What OS is on the server and the workstations?

What is the nature of the table that has changed datestamp, and have its .CDX and .FPT (if present) changed too?

What would be the large volume of users - a number please?

Are you confident in the "construction"/maintenance of the network? Bad networks can cause real strange problems.

Good luck


>Hi,
>I have a program that is automated to run every night. It brings data from a HP database to FoxPro tables. Yesterday morning we had verified that the extracts were completed by checking the tables and verifying the log files that we create.
>
>There is another application A.exe, that queries these tables quring the day. Our users are able to work on this application all morning. But after 1:00 in the afternoon, they seem to get all sorts of erros like 'Structural cdx not found','File access denied' etc. This application is read only. The users see their query results on grids and all the grids are read only. When we checked the tables through windows explorer, we noticed that while all the tables in my database Data.dbc, have the same dates and time (date and time when data was extracted to it the previous night), one of them had been modified the next day afternoon. I am kind of puzzled how this can happen. We have a large volume of users accssing the system between 1-2 in the afternoon. Is there any possibility that this could somehow affect the application?
>
>I believe that since just the .dbf file got modified somehow, the users got the error 'Structural cdx not found'(the corresponding .cdx file had a differnt date & time).
>
>The users do not have FoxPro. Is it likely that, someone could taper the table through windows explorer. I am certain that the extracts did not kick off accidentally around the same time the users started having problems, becaues, my log files would have indicated this.
>
>I know this information is too vague, but please give me your suggestions on how we can possibly figure out what could be going wrong.
>
>Ria