insert block with object DBX

[MikeJarosz]

I have written a VBA routine using object DBX that inserts issue information onto the border sheet. It works well and is super fast, with one exception. The attributes of the block are justified middle center. Unfortunately, they loose their justification when inserted by oDBX.

Here's a portion of the code:

Set BlockReference = oDBX.PaperSpace.InsertBlock(Ipt, IssueBlock, 1#, 1#, 1#, 0#)
    'BlockReference.Update
    For Each Attrib In BlockReference.GetAttributes
    With Attrib
        Select Case UCase(.TagString)
            Case "REV"
                .TextString = IssueFields(0)
            Case "DESCRIPTION"
                .TextString = IssueFields(1)
            Case "DATE"
                .TextString = IssueFields(2)
            Case "DWN"
                .TextString = IssueFields(3)
            Case "CHKD"
                .TextString = IssueFields(4)
            Case "APD1"
                .TextString = IssueFields(5)
            Case "APD2"
                .TextString = IssueFields(6)
        End Select
    End With
    Next Attrib

The block update is commented out because it appears to have no effect on the insertion.

Attached is a snapshot of the result. The first three issues were inserted manually, the fourth by my program. The real irony is that if I open the file in Acad and click the new block to edit it, then close the edit, the attributes jump into position. I suspect the problem is that oDBX can't deal with the justification positions.

Any ideas for workarounds? This program is to update over 1100 sheets, which currently takes about 4 days of manual labor!

[Ed Jobe]

Without a the graphics editor loaded, there's certain calculations that obdx just can't do. Why not move this part to a different process that doesn't use obdx. You can still automate it just the same and it would only be slightly slower.

[MikeJarosz]

Shouldn't the visual appearance of the attributes correct themselves when the file is subsequently opened in Acad?

Like I mentioned above, the attributes do fix themselves if I open and close block edit in Acad, but this action requires user response and is useless in a batch processor.

One of the attractions of using DBX is the fact that these drawings are stuffed full of xrefs, some of which come from a remote office over a Steelhead connection. With no xrefs to load, the whole process flies....

[Ed Jobe]

Shouldn't the visual appearance of the attributes correct themselves when the file is subsequently opened in Acad?

That is standard behavior for atts, they don't move.

A couple of other options:
Use BATTMAN, then the SYNC button to home the atts.
Change the tb to use all left justified atts. All justifications other than Left, require coordinate system calcs to figure out the AlignmentPoint property.

[erikjenson]

I have noticed this similar shifty attribute behaviour. I find sometimes it is even caused by the block editor. The best solution I have found is to "edit block in place" and close either with or without saving. Both seem to correct this shiftyness.

Perhaps you can add the afore mentioned process to your code in the form of a LISP or script to run after the update and before you save and close.

Of course, this comes likely well after you have already solved the issue. But thought I'd put in my 2 cents, just in case.

[RobertB]

Perhaps you can add the afore mentioned process to your code in the form of a LISP or script to run after the update and before you save and close.

You cannot run LISP or scripts in an ObjectDBX document. There is no context for such a thing in just the database.

[hansmartineikerol684707]

Is there any solution to this thread? I'm struggling with the exact same problem these days. ATTSYNC and BATTMAN cannot be run on ODBX-objects it seems, and I'd really love to find a way to upgrade the remote sheets without opening them?

[BlackBox]

Is there any solution to this thread? I'm struggling with the exact same problem these days. ATTSYNC and BATTMAN cannot be run on ODBX-objects it seems, and I'd really love to find a way to upgrade the remote sheets without opening them?

Welcome to AUGI.

If you need to execute either LISP, Script, .NET code within a drawing - without opening said drawing in the main application's Editor - then you'd need to use Core Console in 2013+.

Cheers



Thread officially zombified.