Autocad 2015/2016 - Create new tablestyle method throwing error

[Anonymous]

We are creating the table from Excel 2010 - everything used to work until AutoCAD 2016 was installed or so we think.

Error message received:

---------------------------
Microsoft Excel
---------------------------
AcRxClassName entry is not in the system registry

Error Number: -2145320940
---------------------------
OK   
---------------------------

Code Excerpts

' Grab the tablestyle dictionary object
 Set oDict = adoc.Database.Dictionaries.Item("ACAD_tablestyle")

 sClassName = "AcDbTableStyle"
.
.
.
    ' Check to see if the substation tablestyle has already been created
    If Not (tblStyleChkFlag(adoc, "DwgList")) Then
        'create the TableStyle object in the dictionary
        Set oTblSty = oDict.AddObject("DwgList", sClassName)

Function to check for Table Style

' Function to check and see if a table style exists in a drawing
Public Function tblStyleChkFlag(acadDoc As AcadDocument, tblStyleChk As String) As Boolean

Dim sKeyname As String
Dim sClassName As String

Dim oDict As AcadDictionary
Dim oTblSty As acadTableStyle

' Grab the tablestyle dictionary object
     Set oDict = acadDoc.Database.Dictionaries.Item("acad_tablestyle")
    
    ' Check to see if the tablestyle already exists
    For Each oTblSty In oDict
        If oTblSty.name = tblStyleChk Then
            tblStyleChkFlag = True
            Exit For
        Else
            tblStyleChkFlag = False
        End If
    Next oTblSty

End Function

Registry Settings

Pulling my hair out...or perhaps I'm just going bald?

Anyway, anybody have any words of wisdom?

Thanks in advance.

Mike

[Ed__Jobe]

Probably due to the fact that Office 2010 is 32bit and acad is 64bit.

[Anonymous]

Used to work - last month. With AutoCAD 2015 - never had an issue until I installed 2016.

[Ed__Jobe]

Have you checked your project's references to make sure you're still referencing the correct libary versions?

[Anonymous]

We are showing three library references to the axdblib all of which give the same error when loaded.

1)  AXDBLib | C:\Program Files (x86)\Common Files\Autodesk Shared\axdb20enu.tlb

2) AXDBLib | C:\Program Files\Common Files\Autodesk Shared\axdb20enu.tlb

3) AXDBLib | C:\Program Files\Common Files\Autodesk Shared\axdb21enu.tlb

I have not installed ACAD 2017, but I _did_ have a beta copy of INV 2017 installed.  INV 2017 has been removed - but the problem remains.

IT installed a fresh copy of ACAD 2015 (Vanilla) on a PC running Windows 10 and Office 2010

That PC is using the AXDBlib from C:\Program Files\Common Files\Autodesk Shared\axdb20enu.tlb.

Unfortunately that PC is having issues with the Listview control from VB6 - MSCOMCTL.ocx - so I'm unable to test at this time until that problem is resolved.

Registry settings from a PC with only ACAD 2015.

[HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\ObjectDBX\R20.0\ActiveXCLSID]
"AcDbSortentsTable"="{5EB6721F-506E-4817-B3BF-A4902DDB21AE}"
"AcDbTableStyle"="{73157A89-ABE5-40A5-88E6-C0C94BC718C7}"
"AcDbMLeaderStyle"="{E2C1822C-791C-48BB-AFD0-00890DE860C1}"
"AcDbDictionary"="{8F61C491-AA22-4AB8-8B2D-E24B0AA4303D}"

Once the IT guy (or I) can get the form control issue resolved on the testing PC I'll report back my findings.

[Anonymous]

Success creating new table styles in ACAD 2015 on a 64bit PC running WIN10.

Problem is the ACAD2017 arxdb leftover in the my Registry.

At least I've narrowed down the problem to ACAD not Windows.

[Anonymous · Accepted solution]

Did a reinstall of 2015 - stil getting the same error.

Finally decided to export the registry from the R20.0 ActiveXCLSID on the computer with the fresh install of ACAD 2015.

Before importing the export registry keys I checked each data string to make sure it was a valid key on my PC.

After verifying that the four data strings existed in the Registry on my PC the registry export was imported into my PC and a reboot was performed.

After the reboot the Excel VBA program was again able to function correctly and create new table styles in an ACAD drawing.

Now I just need to port the VBA program to Dot Net...