well, I have recently encountered a runtime error on the second line for
adding a document to an Autocad application after that was set with the New
keyword. It was also a VB program and was run OK and then for no apparent
reason would crash on the second line. after i changed it to CreateObject,
all is well.

i can't figure out why, it's so strange. so i can't be sure this will work
on your case. the MS documentation says that in both my cases, the app
object was early bind since i declared it so like you have, in my case Dim
oApp as acad.application. the documentation continues to say that New and
CreateObject are the same except that CreateObject is slower. so may be,
slower is safer?

reference
http://msdn.microsoft.com/library/de...us/office97/ht
ml/SF7A4.asp

"joan" wrote in message
...
kiat.
thanks for your reply, but theres nothing wrong with the
code. It's been running fine for 2 years, and it runs fine
again after MSExcel is re-installed. I'm sure there's a
dll or something that's getting installed on these PC's or
becoming corrupt, or something like that. I wonder if
anybody can pinpoint that for me?

thanks
joan


-----Original Message-----
I'm not at all sure if this will help, but instead of
New, have you tried
CreateObject? Do a xlApp.Quit before sei it to nothing.

"Joan" wrote in message
...
Excel 97 is being called by a VB program. The behavior
is
this:

Excel opens fine on it's own (from the desktop). But all
of a sudden, on the PC in question, any piece of 'code'
from VB (or event using VBA in MSWord or Access) crashes
with the Error above on the 2nd line of code below:
' Create new hidden instance of Excel.
Set xlApp = New Excel.Application

' Add new workbook to Workbooks collection.
Set wkbNewBook = xlApp.Workbooks.Add

I've read thru all the KB articles and none seem to
apply.

The only way to restore the functionality on the PC is
to
completely unInstall MSExcel, manually removing all the
files associated with it, and then reinstalling. After
the
reinstall of MSExcel the programs all work fine. It
appears that some dll or file is corrupting?

I've tried first just making sure that the MDAC library
was correct, to avoid the uninstall process, and it was
the correct version of MDAC.

It's weird. We have dozens of PCs running the VB
application. And this situation has come up 3 times in
the
past few weeks.

Anybody have a clue?

thanks
Joan


.