Since RealDWG (the new name for ObjectDBX) is pretty much a subset of
ObjectARX, the ObjectARX docs should work for most items. The stuff that
won't be documented is things like creating your own application host to
interact with ObjectDBX.
By and large, you should be able to use RealDWG from either classic C++ or
.NET (using the wrapper assemblies and objects). Note that RealDWG must be
licensed from Autodesk.
If you're satisfied running your application to "edit multiple files without
opening them" from inside of AutoCAD (e.g., ARX/LOAD or NETLOAD), then you
don't need RealDWG.
"Ed Jobe" wrote in message
No, its undocumented. The only place to find info if you're not in ADN is
either this ng, or the vba ng.
Well for example I have 2 projects in mind.
One is a xref renamer.
Scan a project including all subfolders and find all the references to a
Then rename that drawing and have the program update all the sheets to the
The xref manager works nice for paths, but not .dwg names.
It could run inside autocad, doesn't matter to me.
Another application would be to take every drawing on a drive and do a
search and replace.
Say all your drawings were under F:\Job and you wanted to move everything to
Using the reference manager would take months. I'm thinking of a ObjectDBX
do this in hours if it could scan an entire drive.
One big problem with my company is each office uses different drive letters.
We expand our company
by purchasing companies. When we take over we allow the purchased company
to continue with their
existing server structure and standards. This makes collobration between
offices a huge problem.
These are just 2 examples.
I have a grasp of lisp but my developer wants to only work in dotnet because
its new and cool. So I need
to learn how to talk dotnet. I have no desiger to be a coder but I need to
direct him in what I want done.
"James Buzbee" wrote in message
I've been utilizing ObjectDBX via AutoLISP since R2002. What do you want to
As you can see, pretty much everything is availble as if the document was
opened by AutoCAD. So your XREF program could easily access the Blocks
collection and revise saved paths easily. Your programmer should easily be
able to convert AutoCAD VBA into VB.NET - I mean if I could write a similar
program in plain AutoLISP then surely the mighty DON NET won't be a problem!