It is important to educate the user on the differences between DOS and Windows apps. When you ported your app, did you change the menus that the client had become accustomed to over 10 years?

However, I take the stand that once the client is educated as to why or why not something should be done a particular way and they still want it done their way, then do it. But to do it without educating the user client, IMO, is plain wrong.

>Hi Craig,
>
>I'm going to disagree here. Having customers that have used our products for 10 years and evolved into a VFP7 app from FPD26, some things are user preference and if it pays the bills, the user IS right when there is no damage to the app and it does not impact performance in anyway in implementing it. An example is one issue we have with blinking text also. We have forms that display insurance profiles and coverage suspenses were always flagged using blinking text in FPD26. When the app was upgraded to VFP7 the customers actually considered going to another source solely because of no blinking text because they had come to rely on it for 10 years AND competitive vendors offered it in their products. We are definitely not going to force the customer into windows gui standards because the customer would go elsewhere for the product instead. While I agree with you on principle, economics say add blinking text.
>
>Tracy
>