Promised to come back to this later... well, later is now... i have NOT field tested this , not enough hours in a day. This routine was never meant to have much practical use , just a test how to be able to redefine blocks under different situations , using Lisp/Objectdbx , script or using core console (single & multiple). The 'Lisp/Objectdbx' mode works by first renaming the block in the target drawing(s) , then insert the new one on top, do some identity theft (copy propies from old block) and finally delete the old block. Was hoping I would be finished here but sometimes can be a bit slow. So I decided to also try the old school way by using -insert myblock=c:\temp\myblock.dwg. Very boring so decided to have the option to use a standard script , use core console script single mode (.bat file) and multi culti core console (multiple cores at the same time). This works by first wblocking all selected blocks in source document to a temporal wblock folder and insert/redefine them from there.
Don't think I will be using this routine much ... just wrote this to fill a few idle hours between projects. Oh , allmost forgot , not sure the [match] button works as intended because as I said earlier , untested because so far haven't got to it. Visibility for example doesn't work yet. Also , even if it works , this only works when routine is running in Lisp/objectdbx mode obviously (duh) because all the other modes uses script and -insert command. The wb-all button wblocks a complete folder. Got a load of drawings one day from a vendor and wanted to wblock all blocks from all drawings from all (sub)folders to a special wblock folder so I would have a library of all used blocks.
And yes I know about AutoCad built in design center but that's not what this routine is all about.
So maybe someone says , thanx , nice , can use this (assuming it works) and else ... you can thrashcan...yes you can
RlxBlockSyncTest.zip
RlxBlockSync.lsp