DBX modules are meant to be object enablers that provide no UI and can run
in any host application such as Acad LT or Revit. If you never plan to run
your application other than in Acad, or if you want to have UI, then you
should make it an ARX. If you need to access functionality that is only
available in Acad (such as the acedXXX functions) then you absolutely should
make it an ARX.
wrote in message news:6277236@discussion.autodesk.com...
Hi,
I am creating a custom object in order to store persistent data, and I am
planning on storing it in the NOD. I was planning on creating it in a DBX
project but I was looking at the custobj_db sample and I see that it is
implemented directly in the ARX. So I was wondering, since this will not be
derived from an AcDbEntity but an AcDbObject, there will be nothing visible
to be displayed. So maybe it make more sense to implement it in the ARX.
I was wondering if anyone has any thoughts on this? Is it overkill to create
a DBX just to store configuration data?
Thanks!
Joseph
