I installed vba enabler on a new computer in order to test out our old vba plotting scripts in windows 7 x64.
The script worked perfectly, but with the vba enabler arose another problem:
Whenever autocad loads the vba subsystem after I use a command like vbaide or vbaload (even without loading any script) Autocad cannot be restored from windows taskbar after minimizing. Not by clicking task bar or by alt+tab. Only way to restore or close it is by using task manager.
Once I restore autocad using task manager it works well, as long as I don't minimize it again. Restarting autocad solves the problem until you load the vba subsystem again. Killing vba server process in taskmanager while autocad is still running doesn't help.
This effectively prevents us from using any the scripts on about a half of the computers in our office.
Has anyone come across this problem?
Any suggestions how to solve the problem?
I managed to replicate the problem with vista 64-bit. In vista (unlike windows 7) there is a taskbar context menu option to restore the window, which seems to work.
Edited by: anttikauppi3482 on Mar 1, 2010 10:47 AM
The problem was present with vista 64-bit, and is even worse with Windows 7 64-bit.
This is a major problem, since as soon as Acad gets minimized it gets stuck in the toolbar. With no way to ever get it back.(or is there a way to config Windows 7's contextual menu to behave differently?).
I can't close or minimize the VBA window, I can't close or restore the Acad Window. I can't ctrl + Break out of code,
All I can do is Ctrl-Alt-Del and close task.
The problem doesn't exist with Inventor 2010. Inventor.
Any help would be appreciated as this has been a major thorn in my side for quite some while now. And its getting out of hand with Windows 7.
> I installed vba enabler on a new computer in order to test out our
> old vba plotting scripts in windows 7 x64.
> This effectively prevents us from using any the scripts on about a
> half of the computers in our office.
My guess is that Autodesk isn't going to fix this, since VBA is likely
to be removed for good soon.
Time to start porting the code to something else.
> I managed to replicate the problem with vista 64-bit. In vista (unlike windows 7) there is a taskbar context menu option to restore the window, >which seems to work.
That menu still exists with Windows 7 , its just a little more hidden. Mouse over the task bar item until the preview window appears, then right click on THAT window to get the option to restore the Acad Window.
Having to do that everytime the Acad window gets minimized will probably get real old real fast for the end users tho.
As in AutoCAD® 2010, AutoCAD 2011 will not ship with VBA (Microsoft® Visual
Basic® for Applications) module “in the box” – and will require a separate
download. In addition, AutoCAD 2011 will be the last release to include VBA
support. That is, there will be no VBA support in AutoCAD 2012 – just over
one year from now (which means the VBA module will no longer even be
available as a separate download). This applies to all AutoCAD-based
products including AutoCAD® Architecture, AutoCAD® MEP, AutoCAD® Map 3D,
AutoCAD® Civil 3D®, AutoCAD® Mechanical, AutoCAD® Electrical and so on.
Why is it happening?
Microsoft has discontinued the VBA licensing program and made it clear that
they do not plan to provide VBA product enhancements in the future.
Microsoft discontinued the sale of new VBA distribution licenses in July 1,
2007. (Please visit http://msdn.microsoft.com/en-us/isv/bb190538.aspx to read
Microsoft’s statement). This has resulted in our decision to start
discontinuing VBA in Autodesk products now so that we can devote our
resources to more forward-looking technologies.
it would be far more useful for people if suggestions/solutions were offered to this problem, rather than simply saying "get over it & move to .NET". moving to .NET represents a great deal of work for many CAD managers/I.T. managers and it's not as simple as spending a day to make everything new and shiny in .NET and then problems are solved. we understand that VBA is being deprecated, but in the meantime it's still supported because it's still available from Autodesk, even if it's a separate download. it would be great if they would expend some effort as to figuring out how to make it work right in 64-bit for as long as they are going to make it available to use in the current version of AutoCAD.
since i'm sure none of us are holding our breaths for that to happen, what's useful here is suggestions for what might help, not snide remarks about migrating to .NET. if you don't have anything to offer, don't respond. there's plenty of other forums out there that encourage trolls and i'm sure you'll be welcome there.
meanwhile, i am also having this same issue on Windows 7 64-bit. i found another forum post that referred to this issue and someone seemed to think that it related to menu access somehow. i know that we have one VBA macro that loads a CUI file with some custom menus, but disabling the call to this macro didn't change anything. i strongly suspect the problem is with the 64-bit VBA enabler itself, which means it's not likely that any of us (unfortunately) are going to come up with a solution, and only Autodesk is going to be able to solve it, also not likely.
if anyone does have ideas about what the root cause might be and they're solvable by changing the VBA code, please post your suggestions.