BOb,

Indeed..

I remember during the early VFO 2.0 beta that Rushmore would often return negative numbers. Rushmore would return answers before running, or more precicely the running of Rushmore created the original hole in the space-time continueum - but it was still a little unstable. I suspect that it was at that time the Fox Engineers got their first glimmer of Quantum Buffering. This feature was removed, I suspect, in order to give Fox Holdings (the parent company of Fox Software) more time to research this phenomenon. I think it was at this time that Microsoft 'got wind' of what was going on in Perrysburg, Ohio (of all places!) and, after some of their own investigations, decided they'd like to purchase the company. Naturally, Dr. Dave Fulton was a pretty smart cookie and managed to negotiate a merger rather than a purchase. The result, of course, was that this new technology, after the purchase of Fox Holdings was taken and put into the new version of Access. Well, with the dismal results in the 'Access Experiment' the engineers found out that it wasn't a simple matter of 'cut & paste' but a much more sublime case of not only having the right code (Rushmore) but having it find itself in just the right place in memory - as a direct result of the size of the compiled VFP C++ code so as to straddle memory boundaries in such a fashion that the spontaneous emergence of what would now be known as 'Pre-Quantum Buffering'. Personally I also think that the move from using Watcom C to Microsoft C was instrumental. Not that MSFT's C/C++ compilers were faster (we were all worried about this then) but for some strange reason the confluence was perfect and thus the emergence of QB.

The engineers needed to yank this feature for a little while to a) make the sale and b) make sure they had time to research this out to where they could activate it on demand.

I'm just glad to see that the technology didn't get put on the proverbial shelf next to that 500 MPG carbuerator.

>Besides, tests have shown that quantum buffering can only work in write-only memory.