To add to Doug's comment, if you use a GUID instead of the Case ID, which I do agree is a better idea (especially in case you want your attachments saved before the parent ticket is created/submitted); do not forget to index the field containing the GUID on the attachment form.. else a few months down the line when you are using the system with many thousands of attachment records in the attachment form, you are definitely going to have performance problems displaying the table field and retrieving the attachments..
Cheers Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Tanner, Doug Sent: Friday, January 25, 2008 1:48 PM To: [email protected] Subject: Re: Lots of Attachments - RESOLVED ** One additional thing you might want to keep in mind 1.. You may wish to use a GUID instead of the Case ID, If you wish to allow attachments when creating a case and prior to saving J Doug Tanner ---------------------------------------------------------------------------- -- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Gayford, Matthew C. Sent: Friday, January 25, 2008 1:33 PM To: [email protected] Subject: Re: Lots of Attachments - RESOLVED Thanks for all the help and suggestions. I built a separate form and a button to call it from the parent form. The button pushes the request ID to the attachment form on open and a table on the parent form only shows attachments related to that entry. Thanks again! -Matt Matthew C. Gayford Technology Research & Development Information Technology Systems Division University of North Carolina Wilmington (910) 962-7177 From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Tanner, Doug Sent: Friday, January 25, 2008 11:48 AM To: [email protected] Subject: Re: Lots of Attachments ** I am a big believer in having a table field on my form that references another form that holds the attachment. As then 1. I can have an unlimited number of attachments 2. Control access to each attachment – Who can view, edit, remove 3. Enforce Business Rules about when and what types of attachments must be present 4. Auditing 5. In/Out bound email attachments – tying these to the correct record 6. etc Doug Tanner Remedy Skilled Professional (RSP) Former – Remedy Approved Consultant (RAC) ---------------------------------------------------------------------------- -- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Gayford, Matthew C. Sent: Friday, January 25, 2008 11:02 AM To: [email protected] Subject: Lots of Attachments Hello List, I’m building a form on ARS and one of the requirements from the client is an attachment pool. They want to have the ability to add up to 50 attachments. However, not every entry will actually use this many attachments. In fact, most of the requests they enter in this form will not use any of these attachment areas. Anyone have any suggestions for a work around? Or, just any thoughts about the impact of having that many empty attachment areas out there? Regards, -Matt Matthew C. Gayford Technology Research & Development Information Technology Systems Division University of North Carolina Wilmington (910) 962-7177 No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.19.11/1243 - Release Date: 1/25/2008 11:24 AM _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
