Thanks Colin. It's so weird, I thought I noted in one of my examples the single-quotes surrounding the keys (they used to be required in a Pick derivatives). It just didn't seem to work.
I'll say this, I love "^" mode in AE. It's just that the information throws me off all the time. I only seem to edit print files in AE (I use WED otherwise), or imported items, and it always screws up my Wyse 60 emulation screen when I misunderstand that the message means the opposite of what it says. So, when I'm informed unprintable characters aren't shown, I find out they really are and my terminal goes haywire! Then I smack myself on the forehead and say, "jeeze". :-) Bill -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, March 06, 2007 11:02 PM To: [email protected] Subject: {Blocked Content} RE: [U2] UniData ECL anomolies Warning: This message has had one or more attachments removed Warning: (not named). Warning: Please read the "AngelicHost-Attachment-Warning.txt" attachment(s) for more information. Bill; Most of our files use the '*' as a delimiter. One of the first things we learned when we started to move from D3 was to put double quotes around the ID's in the copy line. The UniData eclstyle does work better but like you I have yet to get the hang of it. It's very strange that the "to" portion of the command seems to parse everything properly though. Using double quotes will work - don't use CNAME as suggested elsewhere. I believe on older versions it doesn't update the index. I'm not sure why you don't like "^" mode in AE. It comes in really handy sometimes. Especially when editing _HOLD_ files. Perhaps it's the syntax of the message, I guess it means that unprintable characters are not shown in "^" syntax.... hth Colin Alfke Calgary Canada ________________________________ From: Bill Haskett Bruce: As you saw in my email, I tried both unquoted and single-quoted record keys. Unidata can occasionally get very strange. Most stuff works but sometimes a Pick person keeps knocking their head trying to execute simple commands. For instance, the Prime style "COPY" command has a different syntax than most other commands (apparently the idea was to confuse anyone working in other Pick environments - much like casing is a constant blight for those who work on other environments at the same time they work on Unidata). Using the "LIKE" keyword is a never ending frustration level. The ECL "DELETE" command had to be rewritten to remove the questions asked upon every delete. Don't get me on the AE "^" command that tells me "Unprintable characters not shown" when, in fact, they are. I'm guessing there is a reason I can't change the name of multiple items by using the "COPY" command, but I can't quite figure it out. It's a real bear to move between simple Pick syntax, that is the same for all verbs, and Prime syntax that depends on the verb being used. Bill This is a message from the MailScanner E-Mail Virus Protection Service ---------------------------------------------------------------------- The original e-mail attachment "winmail.dat" was believed to be infected by a virus and has been replaced by this warning message. If you wish to receive a copy of the *infected* attachment, please e-mail helpdesk and include the whole of this message in your request. Alternatively, you can call them, with the contents of this message to hand when you call. At Tue Mar 6 23:04:42 2007 the virus scanner said: Could not parse Outlook Rich Text attachment Note to Help Desk: Look on the AngelicHost MailScanner in /home/virtual/site2/fst/var/spool/mail.quarantine/20070306 (message l2774fLC015475). -- Postmaster MailScanner thanks transtec Computers for their support ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
