<snip>

>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 ?

YES ;-)

It's not easy answering that question. It's up to you to evaluate your future needs. There's something in the making. I don't know if you ever heard of VFPx (VFP extensions). It was previously named Sedna. From what I understood VFPx would be a way to add compatibility between VFP and .Net

So perhaps studying this would help me you more in deciding on your future development environment.

Perhaps you don't need to go with .net for now but knowing what's coming in VFPx would help you make the next version of your accounting package. There could be a way to make it so that the transition later to .net (if or when needed) would be easier and that without affecting your VFP app.

But more on a short term decision. If your customers only buy your software and don't get the source code then it's up to you to see what .net would add to your software. Is it reallt worth it. From what you said apparently not but still you have to make sure it's the case.

It would definetely be easier to write your app in VFP than to do it in .net. But you have to make that BIG decision. What will be best for your enterprise.

Are you ready to take more time and do it in .net or do it faster in VFP. There are two learning curves. I'm sure the VFP would be easier but .net is there and perhaps the timing would be perfect.

Like I told you before not an easy decision. Just be sure you have as much information as you can before making that decision.