Any VBA command crashed Autocad 2002

Any command such as vbarun or vbaman instantly gives autocad a fatal error.
I have uninstalled, wiped the registry and reinstalled autocad 2002 and office 2003
I have also reapplied the patches or service packs for both programs. The machine
is a brand new dell 4600 with XP SP2. I have 4 identical stations deployed without
any issue. But it seems that this one station with this one user roaming profile has
caused some sort of issue with autocad. I could reghost the system, but I am sure
that I would have to whip the users roaming profile also. The problem did not show
itself until the user logged in for the first time. The problem is no longer profile specific as
I have logged with 2 other user accounts and either crashes autocad. I think that
the first time autocad ran it tried to auto install something via the Microsoft office installer.

I have read elsewhere on the Autodesk newsgroups about reapplying an updated scripting
patch or something from Microsoft. I am sure its a Microsoft issue, but reinstalling Autodesk
products do not solve the issue. VBA runs in office without an issue. Its only autocad that
will not run.

David

 

If Office was installed after AutoCAD try reinstalling AutoCAD. In the past I have experienced problems with VBA in AutoCAD (I think it was 2002) when Office 97 was installed after AutoCAD.
Regards - Nathan

 

been there done that. Like I said in the original post Ive removed autocad.

Now I'm having the problem again on a brand new system with win2k, office 2000 and autocad 2002.
Same crash

Nathan Taylor <>
|>If Office was installed after AutoCAD try reinstalling AutoCAD. In the past I have experienced problems with VBA in AutoCAD (I think it was 2002) when Office 97 was installed after AutoCAD.
|>Regards - Nathan


David

 

Did you install Office then AutoCAD or AutoCAD then Office?
Regards - Nathan

 

Nathan is correct! Your problem is well documented within this ng. AutoCAD
HAS to be installed AFTER Office.

-- Mike
___________________________
Mike Tuersley
CADalyst's CAD Clinic
Rand IMAGINiT Technologies
___________________________
the trick is to realize that there is no spoon...

 

Thats what I thought too, but not in my case apparently.

I have a new dell 4600 with office 2003. I installed all the office patches
and then autocad 2002 then the sp1 patch. Autocad launched it said something about
ms office setup and then autocad crashed and would not run anymore.

I uninstalled autocad and reinstalled it to no avail. Machine is still broke

Onto a dell precision 340 with Win2000 and Office 2000. I installed Office 2000 and Outlook 2003
Then I installed Autocad 2002 and the SP1. Autocad would crash on VBAMAN or VBARUN
Reinstalled everything and it did not work. I then removed office and Autocad and installed just
autocad by itself. It ran. Then I installed Office 2000 and it crashed. So I removed it and installed
Office 2003 and now everything works.

So on at least one computer the solution was to install AutoCAD first and then Office.

I have always installed office first then autocad, but in these 2 instances they did not work.
Now onto a precision 470 and I'll see if it works or not.

Mike Tuersley <>
|>Nathan is correct! Your problem is well documented within this ng. AutoCAD
|>HAS to be installed AFTER Office.
|>
|>-- Mike
|>___________________________
|>Mike Tuersley
|>CADalyst's CAD Clinic
|>Rand IMAGINiT Technologies
|>___________________________
|>the trick is to realize that there is no spoon...


David

 

hmmm... the info re: office after autocad is based upon the time which
would have been office 2000. - possible that autocad after office is
skipping some dlls because the 2002 version is older than office2003. guess
you'd need someone with both programs to verify.

-- Mike
___________________________
Mike Tuersley
CADalyst's CAD Clinic
Rand IMAGINiT Technologies
___________________________
the trick is to realize that there is no spoon...

 

well the funny thing is I deployed 4 identical computers with ghost image and they did not
have any problem. I've deployed a bunch of systems with 2003 and 2002 without problems.
So the install order thing does not really hold up. What I really needed from these discussions
is what is the dlls's or whatever for VBA that needs fixing. I'm certain that there is some VBA
dll from Microsoft that can be installed over that would solve the problem

Mike Tuersley <>
|>hmmm... the info re: office after autocad is based upon the time which
|>would have been office 2000. - possible that autocad after office is
|>skipping some dlls because the 2002 version is older than office2003. guess
|>you'd need someone with both programs to verify.
|>
|>-- Mike
|>___________________________
|>Mike Tuersley
|>CADalyst's CAD Clinic
|>Rand IMAGINiT Technologies
|>___________________________
|>the trick is to realize that there is no spoon...


David