Rich, That did not seem to correct the problem. After BWS executes the line of code the extra characters are still present in datastation. Any other ideas? Can I set the encoding on the VB side not to include those characters?
Stephen _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rich McNeil Sent: Tuesday, May 08, 2007 10:59 PM To: [email protected] Subject: RE: [Talk] VB Delimited File problem You're file is being saved in a Unicode UTF-8 format and these characters are put in front of the file to say that...I'd suggest simply reformatting the first field with: D("1") = Replace(D("1"), chr(&hef) & chr(&hbb) & chr(&hbf), "") Rich McNeil Boston Software Systems 866 653 5105 x 813 www.bostonworkstation.com See us at MUSE booth 318 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stephen R. Smesny Sent: Tuesday, May 08, 2007 10:41 PM To: [email protected] Subject: [Talk] VB Delimited File problem I have a VB application that appends data to a delimited txt file. When I open the delimited file in Boston Workstation, D("1") is the following: D("1")=2385. It should be D("1")=2385. When you go to the next record it is fine. The extra characters only appear on the first record. Does anyone know what would cause this? I am assuming it is on the VB side. Is there a way to correct it in datastation or does it have to be corrected on the VB side? Any help is appreciated. Thanks Stephen Smesny ********************************************************************** The information contained in this electronic communication, and any electronic attachment(s), is CONFIDENTIAL and is intended only for the named recipient(s) above. If the reader of this message is not the intended recipient(s), you are hereby notified that any release of information or distribution of this communication is prohibited by law. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender via reply email and delete this communication. ********************************************************************** This message was scanned with MIMESweeper.
