Oplocks will kill us all
Posted: Mon Mar 14, 2011 1:29 pm
Here's the problem we're facing, and it looks like it will affect all/most of you.. I'm looking at this from both a revenue POV as well as a technical POV.
The new quickbooks is SQL based.
Our xbase++ programs are not sql based, and it's not feasible to convert them.. (feasible being defined in months, not years)
If all the oplocks entries are made on a computer, the new quickbooks crashes (we've been told it crashed on a network).
The only way around this we've found is to set-up a virtual XP machine inside windows 7 and make the entries in the virtual machine. But, this is only available to higher $$ windows 7 versions: professional, ultimate and enterprise.
Questions:
1. Any other approaches to the conflicts i mention here ?
2. Theoretically, doesn't oplocks entries need to be made even on a single user machine ??
scenario: 3 separate xbase++ programs which share some databases. if data it entered in 1 and "saved by xbase++", is it visible in the other 2 programs if no oplocks entries are made ?
The new quickbooks is SQL based.
Our xbase++ programs are not sql based, and it's not feasible to convert them.. (feasible being defined in months, not years)
If all the oplocks entries are made on a computer, the new quickbooks crashes (we've been told it crashed on a network).
The only way around this we've found is to set-up a virtual XP machine inside windows 7 and make the entries in the virtual machine. But, this is only available to higher $$ windows 7 versions: professional, ultimate and enterprise.
Questions:
1. Any other approaches to the conflicts i mention here ?
2. Theoretically, doesn't oplocks entries need to be made even on a single user machine ??
scenario: 3 separate xbase++ programs which share some databases. if data it entered in 1 and "saved by xbase++", is it visible in the other 2 programs if no oplocks entries are made ?