Erich-
I did not check for block names specifically, but it does
work for layer names, and the docs imply it applies to all
of the tables. I did a test, and setting the variable does
seem to make new table entries (including blocks) conform to
r14 specs, but does not change existing entries. Drawings
that already have mixed case names will have to be fixed
manually or with code.
Mark Holder
Erich Heiz wrote:
>
> Mark,
>
> Extnames does not any change on this strange behavior.
> The name of the block on the harddisk is in uppercase.
> After the manipulation through VBA (insert, write to attributes) in the
> blocktable the name is in lowercase.
> I do not any Ucase or Lcase in my code.
> I got some minor problems when i search in the table for an existing block,
> thats all.
> So i can use Ucase or Lcase for my search (copmare two string), thats not a
> problem.
> I simply dont like when some undocumented transformations are done?!
>
> Erich Heiz
>
> "Mark Holder" schrieb im Newsbeitrag
> news:38FEFA02.E618978A@atscorporation.com...
> > Erich,
> >
> > Allowing mixed case is one of the new features of A2K. The
> > EXTNAMES system variable can be used to revert to the R14
> > behavior on a per drawing basis.
> >
> > Mark Holder
> >
> > Erich Heiz wrote:
> > >
> > > Hi
> > > is this standard in A2K , that a block name is in lowercase letters
> > >
> > > Set myObj = ThisDrawing.HandleToObject(returnObj.Handle)
> > > myObj.Name
> > >
> > > in Acad14 this was in Uppercase?
> > >
> > > Regards
> > > Erich