>>>>Hey, it's ALWAYS Foxpro's fault (grin)
>>>
>>>As I recall, one of the reasons Microsoft bought FoxPro was to include Rushmore Technology into its preeminent product – Access. You remember Access? That was the database product that would allow any Manager to create a relational database application, to insure that his/her business was profitable. At least that is what the Microsoft salesman told a company I worked for. I never met a Microsoft sales type that heard of FoxPro. Working in Silicon Valley allowed me to meet many.
>>
>>Yes, MicroSoft bought Foxpro so they could gut it and replace it with Access. I still remember waiting the 15 minutes it took for the help file to come up in Access 1.1. Yes, the Access that, even now, really doesn't work well with more than about 6-10 people trying to run the same application, the Access that if the .mdb goes south you've not only lost your data, but your code also. Yeah, that Access. (spit)
>
>The prototype of Access I was shown was so slow, I unwittingly put Fox on Microsoft's radar. The technology did not just go into Access, but into SQL Server as I understand it.
>
So YOU'RE the reason!!!! Get the pitchforks!

Yeah, I remember looking at Access Version 1.something, hit F1 to bring up the help file and waited 15 minutes before I finally killed it. Low and slow is good for cheap cuts of beef and A-10 Warthogs, but not so much for RDBMS's