At 16:40 +0200 2005/09/15, Bjorn Behr wrote:
System: Windows 2003 Server
UniVerse: 10.1.3
I don't know if this is normal, if it is - can someone please explain why.
It is unfortunately normal.
I edited a TYPE 18 FILE WITH 'ed <<FILENAME>> record_name'
and when I saved it, it changed the name to uppercase.
Windows/DOS is case insensitive, non-case preserving. Where as most
Unix sytems are case sensitive, case preserving. The one exception I
know of is Apple's OS X, which is alway case preserving, but if you
save the file on a UFD partition, you'll get case sensitivity, but if
you save the file on a HFS+ (the default partition type) partition,
it will be case insensitive.
I then typed in 'ED FILENAME record_name' and it opened a new record,
but when I went 'ED FILENAME RECORD_NAME' it was there.
Any idea why when I typed in ed in lowercase, it uppercased the record?
It looks like the record ID is converted on the save, so the
lowercase record doesn't exist.
Another Win-U2 oddities, ED/AE won't complain if you create a record
with '*' or any other illegal DOS filename characters, but if it's in
a Type 1, 19 or DIR type file, you'll never be able to access the
record again.
Ray
--
.=================================================================.
| =-=-=-=-=-=-= Eagle Rock Information Systems Corp =-=-=-=-=-=-= |
| -=-=-=-=-=-=- web and database business solutions -=-=-=-=-=-=- |
| <http://www.eriscorp.com> <mailto:[EMAIL PROTECTED]> |
|Midwest Regional Office: 815-547-0662 (voice) 815-547-0353 (Fax)|
.=================================================================.
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
