A bit short a full load, I see that the code I posted still leaves the old
x-data attached.
I will get back when I know something.
"Jim Short" wrote in message
news:BBF0D7A86F051AF6791A8E590EBA44C1@in.WebX.maYIadrTaRb...
> John,
> Thanks for your tip. I tried the empty list suggestion but maybe I didn't
do
> it right. It worked out for me that an entmod with the xdata stripped from
> the elist cleared the xdata. Then I added new x-data with a new appid.
>
> The routine attached is what I ended up with. Function has two arguments
> that are not case sensitive: old and new appid names
>
> (appid-update "OldName" "NewName")
>
> Returns nil if no blocks to update otherwise the entmod elist. I include
> some supporting functions and hope I covered all that were called.
> Jim
>
>
> "Jon Fleming" wrote in message
> news:VA.00001127.0a343d46@fleming-group.com...
> > I think that would wind up with two XDATA lists attached to each entity.
> >
> > For each insert in the list, entmod the insert with the old APPID and an
> > empty XDATA list, then entmod the insert with the new APPID and the
> non-empty
> > XDATA list.
> >
> > jrf
> > Member of the Autodesk Discussion Forum Moderator Program
> > Please do not email questions unless you wish to hire my services
> >
> > In article <2FCE9A454792DEAA74613A85BC2D80BA@in.WebX.maYIadrTaRb>, Jim
> Short
> > wrote:
> > > Hi there,
> > >
> > > I am thinking about replacing the appid on xdata attached to block
> inserts
> > > in legacy drawings. I want to match a new app name. Would some one
care
> > > share this experience or technique. I'd like to save programming
effort
> for
> > > more important chores.
> > >
> > > It looks like if would go something like this.
> > > If drawing contains old appid name, get all the blocks with this
xdata.
> > > Foreach block in the list, retrieve the assoc list and substitute the
> new
> > > name for the old name, then entmod the block.
> > >
> > > Jim
> > >
> >
> >
>
>