AutoCAD Map 2005 3D gives error on close.

[mathew.worland]

We have several people running Map 3D 2005 and a few of them receive errors when closing Map.

AutoCAD Error Report:

A problem has caused AutoCAD to close unexpectedly. Autodesk apologies for any inconvenience this may cause.

There's no error number and they have the choice to send or not send a report.

Any thoughts on causes or fixes.

Thanks,
Matt

[mjfarrell]

Do you have other AutoDesk products installed?
Sounds like a potential installation order issue.
Do you have latest service patch(es) installed?
Are they saving large files to their local hard drive?

[mathew.worland]

Some also have LDD installed
Yes they have the the latest SP
No, the files are saved on a network or are small files saved on the harddrive.

[mjfarrell]

Is the problem isolated to any point of commonality?
Same users? Same files? Same processes?

Was Land installed prior to MAP 3d?

[mathew.worland]

We think we may have it figured out. The commonality is that they load their VBA when AutoCAD loads, and I load mine on demand. One of the guys sent an email to AutoDesk and here is there response.

Quote

'Sorry I haven’t contacted you the problem you’ve been experiencing. We found that if you have VBA scripts being loaded on start up Map 3D will generate a FATAL ERROR when you close it. The workaround solution is to unload the VBA scripts via the Tools > Load Application utility. You can load VBA scripts in a session and use them without any problems on exiting. The problem only seems to occur when you load them when starting Map. I have logged a defect and our Development Team is looking into it. Thanks for your help in tracking this down."

End Quote.

This has not been tested by our department, but AutoDesk thinks this is it.

Thank you again for your help Mr Farrell.

[tim.ashton]

I am glad to see others having the same problem.
Did this ever get fixed?
I need to have the vba programs in the startup suite.
my users will not put up with having to load the program each time they need it.

[mathew.worland]

We load our vba on demand not which also allows for a faster startup.

Try this from the help files
************************
Runs a VBA macro

Arguments

(vl-vbarun macroname)

macroname

A string naming a loaded VBA macro.

Return Values

macroname

Examples

Load a VBA project file:

_$ (vl-vbaload "c:/program files/AutoCAD 2005/sample/vba/drawline.dvb")"c:\\program files\\AutoCAD 2005\\sample\\vba\\drawline.dvb"Run a macro from the loaded project:

_$ (vl-vbarun "drawline")"drawline"*************************************

Hth
Matt

[tim.ashton]

here is the Autodesk Subscription help response
Dear Tim Ashton,

This is an update to your Support Request. Our product development team has reproduced your reproduced issue. They have tentatively scheduled to deliver a fix in: The next major release of product. The specific release date is unknown, so please use the timing of previous release cycles as a guideline.

Please note: Our quality assurance teams may need to reschedule some fixes. Please rely on the above timeline information as a guideline only and not a guarantee. We appreciate your understanding in this matter.

Best Regards,

Chandavar Rukmaj
Autodesk Subscription Support Team


Do they start from scratch each time they release a product.
Map 2004 looks like a more stable release

[tim.ashton]

doh I was wrong
Map 2004 has issues to
some times the undo will only undo once.
I guess map 5 2002 was a better build

[MHultgren]

I have seen plenty of issues when it comes to the startup suite. Either they don't load at all, or they donn't load until you actually open the APPLOAD dialog, or it causes this.

I set my routines up to load on demand similar to Matthew, but I put the code in a lisp file that is loaded from the ACAD200xdoc.lsp file. This will load my menues, autoload routines and an MNL file that has my lisp listing in it. Or you could look at putting your routines together in a file called acad.dvb and leave it in the support path and it will load the routines for you. I do the same thing with ARX files, I just create a file called acad.rx in a text editor and list the arx routines that I want loaded (with the exxtension) on a separate line for each routine.