Hi Ed,

I would be concerned about allowing a user to modify an 'invoice'. I know you correctly stated that the changes would have to be preserved but I see that as problematic when interfacing to something like Word or Excel. I think that it is much to easy for the user to circumvent any controls I might add to the process.

I would treat the initial report as a 'trial run' that is NOT a report of 'committed' invoices. Then allow the user to make corrections and/or additions as necessary. Once the user is completely satisfied with the output, I would call a 'finalize' process to 'commit' the invoices.

Sometimes there is a need to make 'cosmetic' changes to an invoice that has been recorded in the G/L. Usually I require the user to do a Credit Memo and rebill, but for a cosmetic changes like perhaps the customer PO number I allow the change from within the app.

Hope this helps,

Ken

>>>I have a report that is a customer invoice. The user wants to preview the report then edit or add comments to a memo field before printing. What is a good strategy to use for this?
>>>
>>>Thanks
>>
>>Obviously, preview window is not for editing. You can customize preview toolbar, removing print button, then in your code (after preview is closed) bring up some dialog with editbox to view/edit memo field (hopefully, you use one parent record and memo is part of it) and 'Print' button there. Hopefully, your users will accept it.
>
>I'd disagree with the strategy here, Ed. This sounds like an ideal situation for Word automation - build the report as a Word document, and then pop Word up to make changes as desired. Obviously, if the changes are to be recorded, the resulting Word document would have to be preserved, or the information parsed and stored so that it could be reproduced later.