>I have a customer who is complaining that he can run a sales report at the end of the day and get one total, then
without conducting any additional transactions on any of the workstations, re-run the report 10 or so minutes later and get a different (but correct) total. Suspecting caching, I had him uncheck the box that says “Enable write caching on the disk” on the server. He says the problem still exists. If other workstations are still in the app with tables still open with "un-flushed" data, I could see where this could cause the problem. Is there a setting on the workstations that affects caching that I need to change as well? The DBC and all tables are on the server. TIA!
I would suspect the statement which I marked with bold.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)