<div>
I would not do it this way, as the multiple docs included could get quite large with time.<br />
<br />
I would suggest simply using a Doc link to the previous version. <br />
This makes it easy to append more as needed, with little problems of size, and you can do it all in one RTF field, by simply appending the new doc link as needed.<br />
<br />
&nbsp; &nbsp; <br />
I hope this helps !
</div>


I would not do it this way, as the multiple docs included could get quite large with time.

I would suggest simply using a Doc link to the previous version.
This makes it easy to append more as needed, with little problems of size, and you can do it all in one RTF field, by simply appending the new doc link as needed.

   
I hope this helps !

<div>
This seems reasonable.<br />
<br />
How do I create the doc link to the previous version?
</div>


This seems reasonable.

How do I create the doc link to the previous version?

<div>
<div class="content wysiwyg-content">
i have a specs form that may have several versions. &nbsp;each version must have a non editable copy of the previous versions attachments along with a field where the user can insert a new attachment.<br />
<br />
this form is sent to an approver, and if rejected, the user adds a second attachment. &nbsp;previous attachments remain for document history and auditng purposes.<br />
<br />
i was thinking of having this arrangement :<br />
<br />
AttachmentField &nbsp; &nbsp; &nbsp; ApproversRejectionComments<wbr /><br />
AttachmentField2 &nbsp; &nbsp; ApproversRejectionComments<wbr />2<br />
<br />
the AF2 field would be hidden if Status = approved | if AF3 != &quot;&quot;&nbsp; etc.<br />
<br />
how is this process generally handled? &nbsp;is data copied from one rich text field to another computed rich text field? &nbsp;put into controlled access?<br />
<br />
<br />
<br />

</div>
</div>


i have a specs form that may have several versions.  each version must have a non editable copy of the previous versions attachments along with a field where the user can insert a new attachment.

this form is sent to an approver, and if rejected, the user adds a second attachment.  previous attachments remain for document history and auditng purposes.

i was thinking of having this arrangement :

AttachmentField       ApproversRejectionComments
AttachmentField2     ApproversRejectionComments2

the AF2 field would be hidden if Status = approved | if AF3 != ""  etc.

how is this process generally handled?  is data copied from one rich text field to another computed rich text field?  put into controlled access?





appending attachments to attachment fields \ saving multiple versions of attachments

Lotus Software produced the Lotus 1-2-3 spreadsheet program, and later developed Lotus Notes, a groupware and email system. Following its acquisition by IBM, the Notes and Domino client/server collaborative platform were expanded to include functions such as email, calendars, to-do lists, contacts management, teamrooms, discussion forums, file sharing, microblogging, instant messaging, blogs, and user directories. IBM also release SmartSuite, a comprehensive office suite, and followed that with Symphony, unrelated to the Lotus suite of the same name.