>In general terms, I'd create the manual next. But, the ideal thing to do is to build the manual as you build the app. This helps keep things clear in your head and avoids just this type of situation. It also ensures that the manual reflects *exactly* what the app does instead of just what you *remember*.
>
>Of course, if this is your own *personal* app that you intend to refine and sell, then you've got the luxury of time.
>
>For what it's worth, I've been building apps for 12 years and the only time I used a Powerpoint presentation is to sell the idea of the app, never as end-user documentation.
>
>Also, once you build the manual, you're a few short steps from a help file so you're not duplicating any effort there.
>
>Just my .02
>
>Hope this helps
>
>Larry
>
>>I have an application that is finished. Now I have to make a decsion.
>>What do I do next?
>>
>>Do I do an instruction manual, a help file (WINHELP), a help file(HTML), A presentation (Lotus ScreenCam or MS Powerpoint).
>>
>>Would it be better to have a combination. For example A presentation which could give me the possibility afterwards to make a shorter manual because the presentation would cover the basics while the manual could concentrate on more specifics things like Questions and answers...


Thanks Larry!