General information
Category:
Databases,Tables, Views, Indexing and SQL syntax
Gary,
Maybe you could try to severely restrict the RAM on the 2.6 application so that cacheing is less likely?
There is a SYS() that can do this, though I don't know if it was in 2.6.
good luck
>Hi All:
>
>I have a bit of an odd problem that I am running out of ideas with. One of many 2.6 dbf's resides on a Novell Netware 3.12 box. The data is punched in there by a 2.6 LAN based application. This particular single table is monitored by a VFP process that runs on either Windows2000 or NT boxes. The VFP process (based on the session class) is simply fired by a timer, goes to the top of the 2.6 table (issuing LOCATE) and then simply does a SCAN through the table looking for qualifying entries.
>
>On certain occasions, we know that new data has been pushed in to the 2.6 table (by the 2.6 app) but the VFP process seemingly fails to see this data. Its kinda like its been written by the 2.6 process but not hit the disk. We are issuing FLUSH'es from the 2.6 system after the new table entries are created. If we shut down the VFP process and then re-load it, bingo, it now sees the new table entries and processes the jobs that they trigger.
>
>Any ideas what might be happening here?
>
>VFP7 SP1.
>
>Thanks!
>
>-=Gary
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only