not that I know of....I've always had to strip it :)
On Wed, Jun 25, 2014 at 10:48 AM, Rick Cook <remedyr...@gmail.com> wrote: > ** > Thanks, LJ, that makes sense. Is there a way to copy that file name > without the reference data, to avoid having to strip it? > > Rick > > > On Wed, Jun 25, 2014 at 9:43 AM, LJ LongWing <lj.longw...@gmail.com> > wrote: > >> ** >> Rick, those numbers are not a 'fault'...they are reference data. The >> numbers are >> >> BytesBeforeCompression;BytesAfterCompression;OriginalFileName >> >> I use this information in my system for example to ensure that when >> someone attaches a file, it's not a 0 byte file.... >> >> I also copy the file name to another field, and strip the preceding >> values to get just the file name... >> >> >> On Wed, Jun 25, 2014 at 10:38 AM, Rick Cook <remedyr...@gmail.com> wrote: >> >>> ** >>> I am pushing an attachment from the 7.6.04 HPD:Work Log form to an >>> attachment field on another form (same server). Once there, I copy the >>> Attachment file name to a character field for display. The problem is that >>> the character field then contains something like "3223;815;AttachmentName" >>> instead of just "AttachmentName". >>> >>> I can do the field stripping of the prefix clutter, but I'd prefer to >>> address it at the source if possible. Can someone tell me what those >>> numbers represent and how I might be able to eliminate their transfer at >>> the source? The actual attachment file name doesn't contain those numbers, >>> either at the source or destination. >>> >>> Rick >>> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> >> >> _ARSlist: "Where the Answers Are" and have been for 20 years_ >> > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
