Thanks again for the info.. I will think this through very carefully before I begin. This helps me alot. Sorry about the late reply been in the hospital...

Thanks

>>Hi Eric,
>>
>>Thanks for your thoughts on this. In my case the users might not buy it unless it is very easy to use. This is targeted to a group who will not use it unless it is easy (for them) and saves them time. They most likely have never used a computer before...
>>
>
>IMO, a windows compliant UI and an extremely user friendly UI are not mutually exclusive. Windows UI standards allow for things like toolbars with pictures, wizards, pop-up help windows, etc. But they also dictate things like that all toolbar functionality be duplicated in a menu, frequently used buttons or functions should get shortcuts etc.
>
>You might be thinking along the wrong lines thinking that big buttons are going to make the user interface easier. I have seen apps designed like this: Windows standards are thrown out because "the app has to be easier to use", but the end result was an unintuitive interface that also look stupid. IOW, the two are independent. You can develop an easy interface with or without complying to Windows stndards, but doing it by the book buys you a couple of things: experienced computer users will be at home as well, as users learn to use the app, it doesn't begin to trip on its own feet, and it looks like a windows app.
>
>Be careful when deciding to throw out a standard: IMO, the situation rarely calls for it, and in many cases when the standard is abandoned, it is because the developer didn't know how to make the standard work for him.