>>
>>Hi Craig,
>>
>>I've been pondering this same question lately myself. We converted to SQL Server about three years ago and started moving a lot of our existing VFP/VB desktop apps into the SQL world. We still use VFP to build most of our apps but we are not using it for the backend except in one or two cases where the useful life of the app is about over. I have some small, non-network apps to build and I've considered MSDE for a backend as opposed to VFP.
>>
>>I not sure I can go back to VFP on the backend. Don't get me wrong, VFP is my tool of choice for COM/DCOM servers doing tier two and three work and there's nothing wrong with it for the UI either. My latest app uses VB, VFP, MSMQ, MTS, and SQL Server so I don't think I qualify as a "tool nazi" <g>.
>>
>>What do you see as the disadvantages to using MSDE?
>
>The only real advantage I can see to MSDE over VFP tables is if you will go to SQL Server in the near future. But, even that is not a given. MSDE is optimized for five users. What if you need 10, 15, 20, or 100? Is the cost justification there for getting into SQL Server?

How much value is there to real stored procedures and good database security? Remember, MSDE is scaled for 5 CONCURRENT users, many small businesses can easily cope with that. The problem will be in the mid-size or rapidly growing small business. I agree, SQL will cost more but you get more.

I suppose the best thing to do is to program for any backend, advise the customer of the options, and let them make the decision. That's what n-tier is all about, I suppose.