I have a multiuser inventory application on a Win2K server, NT/98 client network. I've noticed several times that if I change data in a table on one machine, it doesn't appear on another machine for some time (minutes or hours, or possibly until some specific action is taken).
In the most recent instance, I updated a parts list for an assembly on one machine, then on another machine, a user tried to generate a bill of materials (BOM). The BOM form uses PAL to summarize and format the parts list data into a temporary table in the local private directory. So the BOM's code uses tCursors to get the data from the actual tables, but its data model only refers to the private directory table.
I could re-run the BOM code as many times as I wanted, and it would never reflect the updates. But when I opened the form for editing the assembly data (which has the underlying table in its data model), the UI froze for a few seconds. After that I re-ran the BOM, and voila - she is correct!? Does anyone know what's going on here? Who is caching what, and why wouldn't the cache get flushed in this case?
- John
In the most recent instance, I updated a parts list for an assembly on one machine, then on another machine, a user tried to generate a bill of materials (BOM). The BOM form uses PAL to summarize and format the parts list data into a temporary table in the local private directory. So the BOM's code uses tCursors to get the data from the actual tables, but its data model only refers to the private directory table.
I could re-run the BOM code as many times as I wanted, and it would never reflect the updates. But when I opened the form for editing the assembly data (which has the underlying table in its data model), the UI froze for a few seconds. After that I re-ran the BOM, and voila - she is correct!? Does anyone know what's going on here? Who is caching what, and why wouldn't the cache get flushed in this case?
- John