In message
<[EMAIL PROTECTED]>,
[EMAIL PROTECTED] writes
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.
Why? It makes perfect sense to me ... Oh - and this thing with '*' might
well not be a UniData problem. When we tried using some commercial
software to back up our "UniVerse on SCO" system, it barfed HORRIBLY
when it hit the catalog directory - it did not like asterisks in
filenames AT ALL.
If you're specifying record ids to *read* from, wildcards make sense.
'*' is a wildcard in certain circumstances. When specifying records to
write to, wildcards don't (normally) make sense. Hence the problems with
choosing records to copy FROM but not TO.
Prime CPL (or was it Primos Rev 19 syntax) made this distinction clear -
when copying files at the OS level, it used a wildcard character to say
"select any matching files" (which obviously only worked in the "from"
part) and a different wildcard which said "select the matching element
from the 'from' name", which only worked in the "to" part. Neat.
Cheers,
Wol
--
Anthony W. Youngman <[EMAIL PROTECTED]>
'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking the
thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The man
lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998
Visit the MaVerick web-site - <http://www.maverick-dbms.org> Open Source Pick
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
