Hi Sean, Thanks for the response. The problem is that the application on the other end of the web service only accepts ".zip" files. That is why I need to zip these attachments. Thanks!
Greg -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Garrison, Sean (Norcross) Sent: Friday, July 09, 2010 8:55 AM To: [email protected] Subject: Re: Zipping up attachments You don't really have to do this. Remedy compresses the file out of the box. From page 33 of "Using relational databases with AR System": "The Attachment details table contains information for the properties of Attachment fields. For every Attachment field in the form, a separate table is created to store the attachment value. The Attachment details table is named with a B followed by the unique ID for the form (for example, B3). In Figure 1-1 on page 24, the attachment details table is labeled Bn. An attachment details table with one column (C1) is created with every form. For every attachment field added to any attachment pool on the form, three new columns are added. Each column is named with C, CO, or CC, followed by the attachment field ID. For example, the three columns added for one attachment might be called C536870920, CO536870920, and CC536870920, where 536870920 is the attachment field ID. The C column stores the full path name of the attached file. The CO column stores the original size (in bytes) of the attached file. The CC column stores the compressed size (in bytes) of the attachment file." I found this out the hard way when I tried to do a direct extract from the DB of a file. The file never worked and I couldn't figure out why until I read the docs and found out that remedy uses some sort of compression algorithm. Thanks, Sean -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Greg Donalson Sent: Friday, July 09, 2010 9:33 AM To: [email protected] Subject: Zipping up attachments Hi all, I have a requirement that in order to send an attachment across web services, that the attachment must be zipped first. I was wondering if there was any way that once the user has submitted an attachment to go back in and zip the attachment and then send it across web services? I would think that I would have to call an API to extract the attachment and then another procedure to zip it up. I was just wondering if anyone has done anything like this before and if they would not mind sharing how they did it. Thanks in advance! Greg AR Server: 7.01 ITSM: 7.01 Mid-Tier: 7.01 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
