Add references of several autocad versions
Hi,
your issue need a specialists that can help you ... and you will find them here . >> Click <<
Regards,
Imad Habash
You can't do that with a vba dvb because the dvb isn't just the written code, it also includes compiled code. Also, when you load a dvb, the vba environment automatically binds to the version of type library that is currently running. If your dvb was compiled with code for 2014 and you open the dvb in 2018, the 2014 code gets deleted and the dvb project is then updated for the current tlb reference and then recompiled. If you then try to use the same dvb in 2014, you will get the error you described. You need to maintain a dvb for each version of acad you are running.
Ed
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
How to post your code.
You may want to describe what you do clearer, since you mentioned both VBA and using Visual Studio - this 2 usually are not mix-used.
Are you doing AutoCAD VBA development? Why is Visual Studio used? Do you use Visual Studio (assuming with either C# or VB.NET) to generate a COM-able DLLs and use it in AutoCAD VBA? Or, in fact you are not doing AutoCAD VBA, but AutoCAD .NET (with VB.NET)?
Depending on what exactly you are doing, the answer to your question would be quite different.
Well, you still not make it clear enough: using VB.NET doing what: is it an stand-alone EXE app that automates AutoCAD (via AutoCAD COM API) or is it an AutoCAD .NET API add-in (DLL project)?
However, for both cases, in general you can set references to the oldest version of your AutoCAD target versions and expect your code would be work with newer versions of AutoCAD, as long as the "oldest" is not that too old. For example, if you develop against AutoCAD 2015, your code most likely work OK all the way up to AutoCAD 2019.
Again, you did not say what type of project you are doing (EXE or DLL add-in), the only thing I could say is, yes, if you program against AutoCAD2014, the code would very LIKELY work OK with later versions of AutoCAD, but not 100% guaranteed, you need to do thorough test on each target later version.
VBA6? Which version of AutoCAD do you use? It has been VBA 7 since AutoCAD 2015. If you are really talking about AutoCAD VBA, which is built-in with AutoCAD (even it is a separate installation), it is tied to which ever the AutoCAD version is. You do not add references to AutoCAD's type library of different version.
Maybe you actually mean VB6 (a.k.a. classical Visual Basic)? and you want to build an EXE to automate AutoCAD? There is no way to add references of multiple AutoCAD versions at the same time.
You may want to explain what you want to do in detail and what you use (VBA in AUtoCAD, or VB classical or VB.NET)...
If you are talking AutoCAD VBA, you DO NOT add reference to AutoCAD type library, AutoCAD VBA add it automatically and you CANNOT change it. See picture below: the red-circle reference is FIXED and cannot be changed:
Again, you better explain what you want to do/achieve, rather than just saying something that you should not do (adding different version of Acad reference) in AutoCAD VBA. But let me guess: you write VBA code in AutoCAD 2013 (which has Acad2013 type library referenced, of course). Then you want to a user with AutoCAD 2018 64-bit to run your VBA project and the code does not run?
If that is the case, as long as the said Acad2018 is 32-bit, your VBA project might run OK. However, who runs 32-bit AutoCAD of later versions these days? Almost no one! So, let me assume the user uses 64-bit AutoCAD (2018, or whatever). Thus, the code would most likely not work until you actually open the VBA project in AutoCAD and do some fixes, because VBA in 2013 is 32-bit. Note, depending on what the VBA project does, the required fixes vary. The point is, you need to open the VBA project in a 64-bit AutoCAD/VBA and open the "References" dialog box to fix any references flagged "Missing" and then save the VBA project. After that, the VBA project would likely work with mutiple version of AutoCAD of 64-bit without any change.
