>A bit of devils advocacy here... I agree in theory but I think part of the situation is that VFP has a pretty steep learning curve and that the small/mid-size shops typically are not heavy into custom development. So Microsoft may respond that the tool you are talking about for small/mid-sized database work is Access, not VFP.
>
>I believe if Access wasn't in the picture VFP maybe able to play better in the small, mid-sized market. But with Access grabing the low end, entry level database market and .NET/SQL Server going for the enterprise it sort of squeezes the fox in the middle.

Maybe, but then they would have to own licenses of MS Office which they may or may not already have or want top buy ( alittle bloated if all you want is MSAccess). With VFP they do not have to buy the product, just pay the developer for their work, who inturns delivers them a solution woth the proper runtimes.

Maybe that's where the economic (revenue model) problem lies! <g>