Just a bit extra info, which may not be much of help:
You say
<QUOTE>
- with the "CLngPtr" the compile error would highlight ".CLngPtr" part
</QUOTE>
I am bit confused: CLngPtr() is a global function, not a function of an Object. So, why the ".", which would obviously cause compiling error for sure. If the "." is simply typing error in your post, then are you saying the code like this:
myTable.SetBlockTableRecordId j + 1, 0, CLngPtr(myDoc.Blocks("blockName").ObjectID)
still gives compiling error by highlight ClngPtr()?
Here is what I get with my stand-alone Excel 2016 from MS Office 2016 suite (also VBA7.1 32 bit)
I wrote a few line of code to set up an AcadTable with one line calling
myTable.SetBlockTableRecordId(..., [BlockId],..)
Regardless [BlockId] is wrapped with ClngPtr or not, as soon as I compile the code (menu=>Debug->Compile...), VBA IDE freezes, I have to kill AutoCAD.
If I comment out that line of code, compiling/running is OK.
You see the difference here: you could at least compile with your Excel in Office 365, even it does not pass; On my side, compiling itself would crash AutoCAD VBA when that particular line of code exists.
So, I'd likely give up the idea of running Excel VBA code to automate AutoCAD because of this, if I were you.