My company used autocad 2009 and a printing Plug-in which was made by VB,they worked perfect.But when my company uses autocad 2010,the problem rises:The printing Plug-in doesn't work.
Although I downloaded and installed the Microsoft Visual Basic for Applications Module 32bit (from http://usa.autodesk.com/adsk/servlet/item?siteID=1
Firstly I install autocad 2010,then VBA,next printing Plug-in.Is there anything wrong?
Please help me out!
Any help will be appreciated.Thanks in advance!
Best regards Wilson
>> [...] printing Plug-in which was made by VB [...]
First you should not mix up "VB" and "VBA"! Having a VB-developed application could be an EXE- or a DLL-file, VBA has DVB as file-extension.
Secondly what does the developer of this tool say? Or havn't you asked him/her?
How was the tool loaded into your AutoCAD 2009 version? And in short words: what does the tool (because printing or plotting could be done with AutoCAD and without an application).
- alfred -
AutoCAD 2010 breaks binary compatibility with previous releases
You will need to update your references for 2010 and the VB application may not function if your running 64 bit windows.
Thanks for you reply.
The printing plug-in is VB developed ,and autocad 2010 should support that just like what 2009 supports.When I press 'eplot' in 2009 command window,a printing window will pop up just like what 'plot' works.But the situation is that in 2010, even after I install theMicrosoft Visual Basic for Applications Module ,nothing happens,2010 can not recognize the eplot command. The plug-in supplier say It's the problem of 2010, because the VB enabler is that loaded in 2010,after installing the Microsoft Visual Basic for Applications Module ,problem can be sovled.But magic doesn't show up=(.
What's wrong with it?Could you help me out?
Thanks for the reply,buddy! I'm running 32 bit autocad. The problem is that autocad 2010 couldn't supprt VB developed plug-in,however the version before 2010 works fine.
>> The printing plug-in is VB developed
So it has to be modified - arcticad told you - the references within the old EXE/DLL points to 2009-library and that's not compatible to 2010. You have to open the sourcefiles of the application, change the references (hope that is all to change) and recompile it.
Good luck, - alfred -
Access a broad range of knowledge to help get the most out of your products and services.