>It's enlighting to not that VFP back-end is STILL used for mission critical applications. Perception is Dbf=data curruption.

Yes, it is also the story in one of my clients right now. As for me, I don't rememeber the last time it happened.

>Our next version of Accounting software will just have Windows GUI & Windows printing ( Laser printer support ) & support for dbf/server storage. No Web interface, no mobile support, no PDA support.
>
>Do you think VFP would be a good choice ?

It sure will be, as it has always been.

>Can you also elobrate on "Because its maintenance in regards to the way I do it is much faster." ( Please )

Well, first of all, SQL Server keeps changing its interface, which also make it difficult to get use to it. There are so many components and it also depends on what you install. Recently, I faced a situation that I thought everything was installed, as I did it from the default setup.exe on the CD and ended in a situation that I almost had nothing. Then, after having installed all the components, it was a question of knowing where they are. In VFP, you go in VFP and everything is there. That is simple. In a general overview, I think it makes sense.

Oh yeah, VFP as command prompt. There is certainly one somewhere in SQL Server but it is still light years behind VFP.

And, when I want to made some test programs, data maintenance and other related needs, I don't have to work in Client Server mode. We have local data and this is what I need in those circumstances. This is a real time saver. For example, in the last 16 hour shift I did tonight, with all the data manipulation I did, it would have taken me between 32 and 40 hours in Client Server.

Those are just a few things that are important for me. I am sure many could elaborate more on the topic.