Hi Jim,

I'm sorry, but I have to disagree with you.

>I think this is one **BIG** point of "confusion" (actually, I'd call it deception) as regards deployment of MSDE.

Where is the deception? Go the the MS Site and read all about MSDE - all the facts are available for anyone who wants to read them.

>
>That means that you have NO WAY to set up MSDE for your aplication without having SQL Server installed in your development system and you have no real way to "work" a problem at the customer site unless they have SQL Server installed.
>
>Sure, there are apparently free or low-cost third party tools that address this issue, but that is not the point - which is that MSDE is free is NOT adequate/HONEST reason to deploy MSDE in favour of DBC/DBF.

If you have an app that may at some point exceed the limiations of MSDE, and explain this to your client (along with the reasons for choosing MSDE) in addition to making sure the client is aware that there may be a requirement to purchase a SQL Server license in the future - how is that being dishonest?

>
>Finally, the alleged simplicity of switching to genuine SQL Server when growth mandates it has been shown to be highly over-simplified and is likely FAR MORE EXPENSIVE than is touted to be.

The cost would be the cost of the applicable licensing package purchased.

>
>I'm sure that MSDE or SQL Server has a perfectly good place with VFP in the business world, but my guess is that that place is far smaller than "promoted", is somewhat more difficult/costly than "promoted" and bring problems not known in the standard DBC/DBF world.

MSDE isn't the answer for everything - use DBC/DBF's all you want - everyone has their own preference. But there is certainly no deception involved with MSDE if you do the research.

>
>Worth every penny of what you pay for it!!!
>