Sadly, we on the developement team were open to several other platforms besides SQL Server, it is not our first choice, mine was Codebase or hybrid VFP tables like Codebase did by increasing the table header size to 64 bits and write our own tools in VC++. I sure like xBase tables. I worked SQL Server before and still have flash-backs ( ha ha ). As I said our clients are pushing us to SQL or Oracle, simply based on name recognition. These are IT people who dictate to our users ( and subsequently have a say in the budget allowances ) which software they can and cannot have. These uninformed, non-software developing people think that Access and SQL Server hung the moon, yeah right. They are whispering things like if we don't change to a more robust client-server backend ( SQL ) they are going to recommend our clients use other packages or develope in-house solutions. The make ignorant arguments like VFP, or Codebase, or MySQL is not "proven" enough in a heavy workload environment and could cause networking problems, data loss, loss of functionality, blah blah... A bunch of novice bunk. This is what happens when 21-24 year old Junior College graduates are put in charge of large server farms, a Napoleon syndrome evolves. IT guys irritate me, we have our own network separate of operations because our IT guys were always in our business. Hacked 'em off when we cut them out.

We are the only supplier in our market, but it is only energy companies, so the pool is small and we have to swim with the current or run a ground. Our only competition to date is the in-house folks who think they can produce in 6 months what we do ( our product has evolved over 10+ years ).