VBA Crashes on XP

[Anonymous]

Is there some sort of problem running VBA on XP
Pro.  Anytime I go to start a VBA that I wrote or get in to the VBA Manager
it crashes.

--
Dave Gardner

[Anonymous]

Hi David,

The fact that Autodesk tells us that none of their products are supported on
XP probably relates to this sort of (relatively) obscure problem.

--




Laurie Comerford
CADApps
www.cadapps.com.au


"David M. Gardner" wrote in message
news:BF979192FFFF14698075DFD73FAA75DB@in.WebX.maYIadrTaRb...
> Is there some sort of problem running VBA on XP Pro. Anytime I go to
start a VBA that I wrote or get in to the VBA Manager it crashes.
>
> --
> Dave Gardner
>

[Anonymous]

That is not true. AutoDesk does support some products on XP. The rest are
in testing. By the way is just started to work out of the blue. I did
nothing and it started to work. Strange eh?

--

Dave Gardner
"Laurie Comerford" wrote in message
news:FCAA30E782F7A206ADD6541FB7930588@in.WebX.maYIadrTaRb...
> Hi David,
>
> The fact that Autodesk tells us that none of their products are supported
on
> XP probably relates to this sort of (relatively) obscure problem.
>
> --
>
>
>
>
> Laurie Comerford
> CADApps
> www.cadapps.com.au
>
>
> "David M. Gardner" wrote in message
> news:BF979192FFFF14698075DFD73FAA75DB@in.WebX.maYIadrTaRb...
> > Is there some sort of problem running VBA on XP Pro. Anytime I go to
> start a VBA that I wrote or get in to the VBA Manager it crashes.
> >
> > --
> > Dave Gardner
> >
>
>

[Anonymous]

David, I found this same problem with XP Pro, Office, and TuTu. If you
install Office (or some components of Office) *after* TuTu, TuTu will hate
you until you reinstall it. Autodesk tells us that AutoCAD has to be
installed *after* Office.

--
R. Robert Bell, MCSE
www.AcadX.com


"David M. Gardner" wrote in message
news:AD4AF28480FFB2C308D82A93D5DA5E01@in.WebX.maYIadrTaRb...
> That is not true. AutoDesk does support some products on XP. The rest
are
> in testing. By the way is just started to work out of the blue. I did
> nothing and it started to work. Strange eh?
>
> --
>
> Dave Gardner
> "Laurie Comerford" wrote in message
> news:FCAA30E782F7A206ADD6541FB7930588@in.WebX.maYIadrTaRb...
> > Hi David,
> >
> > The fact that Autodesk tells us that none of their products are
supported
> on
> > XP probably relates to this sort of (relatively) obscure problem.
> >
> > --
> >
> >
> >
> >
> > Laurie Comerford
> > CADApps
> > www.cadapps.com.au
> >
> >
> > "David M. Gardner" wrote in
message
> > news:BF979192FFFF14698075DFD73FAA75DB@in.WebX.maYIadrTaRb...
> > > Is there some sort of problem running VBA on XP Pro. Anytime I go to
> > start a VBA that I wrote or get in to the VBA Manager it crashes.
> > >
> > > --
> > > Dave Gardner
> > >
> >
> >
>
>

[Anonymous]

I'm running Windows 2000 Pro o/s, Office XP Pro w/service pack 1, and AutoCAD 2000i networked w/client install. I'm also having the same problem using VBA components. I've reinstalled Office, then reinstalled CAD 2000i via our network install, but doens't fix anything. Sometimes Office VBA components work, & sometimes not, but CAD VBA component usage causes CAD to crash. Looking for help.........

[Anonymous]

Try this.  Install Office.  Run Office
VBA via word.  Then install AutoCAD.  Run Office VBA again.  Then
Try AutoCAD VBA.  Good luck.  I did something similar and that
worked.

--

Dave Gardner

style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">

"tspace" <
href="mailto:tspace@duke-energy.com">tspace@duke-energy.com> wrote in
message
href="news:f0aa59d.3@WebX.maYIadrTaRb">news:f0aa59d.3@WebX.maYIadrTaRb...

I'm
running Windows 2000 Pro o/s, Office XP Pro w/service pack 1, and AutoCAD
2000i networked w/client install. I'm also having the same problem using VBA
components. I've reinstalled Office, then reinstalled CAD 2000i via our
network install, but doens't fix anything. Sometimes Office VBA components
work, & sometimes not, but CAD VBA component usage causes CAD to crash.
Looking for help.........

[Anonymous]

I think it's due to your reference of VisualBasic for Applications in your VBA Project.

If you have MSVBVM60.dll, it won't work.You must have VBA332.dll or VBA6.dll.