Save Method in ObjectDBX

That’s an irrelevant question. The problem here is that I'm gettingerror when I use the SaveAs method. If you don’t mind let's stay with that subject.

 

File size is not an issue. I get the error on SaveAs on:
A blank drawing
or a drawing with a single line
or a complete drawing with xrefs and other objects.

 

of course!
me big dummie! what was I thinking?

 

does that line *not* give you an error?

what version of acad are you on?

what library are you referencing in your project?

does the following declaration act any differently?
Private objDbxDoc As AXDB15Lib.AxDbDocument
(and of course then Set objDbxDoc = new AXDB15Lib.AxDbDocument)
or the equivalent Private objDbxDoc As New AXDB15Lib.AxDbDocument

do you want to post the actual code that is not working?

from the bits you've posted it's hard to see why it wouldn't work fine.

 

er...make that
Set objDbxDoc =
AcadApplication.GetInterfaceObject("ObjectDBX.AxDbDocument")
not
Set objDbxDoc = new AXDB15Lib.AxDbDocument

duh!

 

I already tried all these. I'm using 2004 libraries and my code is posted way up there after you requested once before.

 

It's not an irrelevant question.

You're on your own.



AcadX for AutoCAD 2004 Beta 1
http://mysite.verizon.net/~vze2vjds/acadx/AcadX16.zip


That's an irrelevant question. The problem here is that I'm getting error when I use the SaveAs method. If you don't
mind let's stay with that subject.

 

Tony,

Please do not take my comment personal. We are professionals here, in search of an answer and it's important to stay focused on the topic.

The reason your question regarding Xrefs is irrelevant is because as I mentioned probably more than few times, to more than one person, all through this discussion, I am opening a drawing using ObjectDBX (2004) in VB6 and getting an error on SaveAs, right after open method.

I hope you can see now why your question was irrelevant and not inline with the topic of this discussion.

 

I found the answer. I'm posting it here just incase someone else comes across this same issue.

After opening AutoCAD I was closing the initial drawing (Leaving it in "thegray background" state)

When AutoCAD is in this state, ObjectDBX works fine to open other drawings and read from them, even create layers and other possible changes. However,it raises error when you try to delete (Layers, TextStyles) or use SaveAs.

I left the default drawing alone and problem got solved.

Strange, isn’t it?

 

Not particularly

Internally AutoCAD uses the current database for many things especially
when working with table records.

The 'zero-document' state has a NULL current database. It's a pretty
unstable environment to do any database related work.

--
Best regards,

Byron Blattel
CADwerx--Applications for AutoCAD
Autodesk Registered Developer
Contact Info @ http://www.cadwerx.net
Custom Programming Services - ObjectARX/C++/MFC/ASP/STL/ATL/ISAPI...

 

I understand, but I have to stay on my comment regarding this being "Strange". It's hard to accept the word "unstable" when it comes to software. However, it is easy to accept "Not completely implemented yet". I am not going to use the zero-document state in my projects anymore, but my point is if I am able to add a layer in this state, and be able to verify that the layer is added, I should also be able to delete it.

 

Welcome to the real world !!

--
Saludos, Ing. Jorge Jimenez, SICAD S.A., Costa Rica

"Strange". It's hard to accept the word "unstable" when it comes to
software. However, it is easy to accept "Not completely implemented yet". I
am not going to use the zero-document state in my projects anymore, but my
point is if I am able to add a layer in this state, and be able to verify
that the layer is added, I should also be able to delete it.

 

Strange, I find it hard to accept your tone.

--
Best regards,

Byron Blattel
CADwerx--Applications for AutoCAD
Autodesk Registered Developer
Contact Info @ http://www.cadwerx.net
Custom Programming Services - ObjectARX/C++/MFC/ASP/STL/ATL/ISAPI...

 

axvoskan,

You need to remember that the contributors in here are volunteering their time to help people such as yourself resolve problems. "We" are not in search of an answer - "you" are. Tony is very experienced and you can bet if he asked a question about your problem that it had some significance, even if you yourself couldn't see it. Scolding him like a schoolboy is both rude and detrimental to your own cause.

My impartial observation.

Wayne Ivory
IT Analyst Programmer
Wespine Industries Pty Ltd