Inventor.Circle vs Circle

[nedeljko.sovljanski]

Hi,

Does anybody know why declaration for Circle must be done with

Dim oCircle as Inventor.Circle

instead of

Dim oCircle as Circle?

[bradeneuropeArthur]

Because it is used in another object too.

[nedeljko.sovljanski]

Hi,

I agree that is used in another object but I can not find in which.

[bradeneuropeArthur]

I don't see a difference.

Could you share the code you have problems with?

[nedeljko.sovljanski]

There is no particular problem but I am interested why in VBA it is necessary to use Inventor.Circle (and only for Circle) and in C# Inventor is redundant declaration.

For some newbies in macro writing in VBA it can be confusing, so I want someone to clarify.

[JelteDeJong]

I could reproduce the "problem" but I could not find why. Usually, you need to add the namespace for an object type if the compiler does not know which namespace should be used. That implies that there is another namespace with the object "Circle" but I  could not find such namespace.

But if you are learning VBA then I would advise you to stop and start learning VB.net/iLogic. This is what Autodesk writes about VBA:

"For security reasons, the Microsoft VBA module is not included in the Inventor installer. It has a dependency on the Visual Studio 2010 (VC10) runtime, which Microsoft will not support after July 2020."

and

"As an alternative to VBA, consider using Inventor’s iLogic capability. It provides access to the Inventor API using VB.NET."

That sounds to me like the end of VBA and not something that I would put any effort in.

[WCrihfield · Accepted solution]

I see that Access (Microsoft Access) has a Class called Report, and Circle is a Member (Sub) of that  (Access.Report.Circle())

[nedeljko.sovljanski]

That is answer I am looking for. Thank you very much!