M
Mike MacSween
Office 2000
From Access I've been starting an instance of word and doing a mail merge.
Everything hunky-dory until I applied SP1 yesterday.
Now this:
dim wrd as Object
set wrd = CreateObject("Word.Application")
Produces an out of memory error.
My code is a lot longer than that, but I've stripped it down and created a
new module to isolate. I've done umpteen uninstalls, used the eraser,
reinstalled etc. etc. Word itself starts OK if I start it on it's own. It's
as though there's some supporting dll or something that is needed when Word
is used as an automation server. This happens even with a brand new mdb
created on the target machine.
I had something similar a while ago, infact the symptoms were exactly the
same, just that the error message was 'error loading dll' - see that thread
'References Screwed Up'. I tried everything I could think of then. In the
end I gave up and reformatted and re-installed. Obviously I shouldn't have
to do that, and it's not really an option on 10 client machines. I've just
tried it on a Windows 98 machine (Office 2K unpatched) with no problems.
Interestingly I thought the Office 2K SR1 had been applied to this machine,
help/about said so. But when I started Speed Ferret yesterday it claimed
that it was an unpatched version of office (which has a bug that can cause
data loss when using SF, they say) even though it says SR1 on help about. In
other words that Office 2K will misreport itself as having the patch, that
it's the actual build number that counts. BUT on the version on Windows 98
help/about reports itself as not being patched. These versions will have
been installed from the same CD (er, one desktop, one laptop, still within
the licence). So how come one version was reporting itself as patched when
SF said it wasn't? Which shouldn't of course matter, I've just patched it
twice. But this is the problem somewhere isn't it. Some dll or olb or
something has got damaged or overwritten and I can't get it back.
TIA, Mike MacSween
From Access I've been starting an instance of word and doing a mail merge.
Everything hunky-dory until I applied SP1 yesterday.
Now this:
dim wrd as Object
set wrd = CreateObject("Word.Application")
Produces an out of memory error.
My code is a lot longer than that, but I've stripped it down and created a
new module to isolate. I've done umpteen uninstalls, used the eraser,
reinstalled etc. etc. Word itself starts OK if I start it on it's own. It's
as though there's some supporting dll or something that is needed when Word
is used as an automation server. This happens even with a brand new mdb
created on the target machine.
I had something similar a while ago, infact the symptoms were exactly the
same, just that the error message was 'error loading dll' - see that thread
'References Screwed Up'. I tried everything I could think of then. In the
end I gave up and reformatted and re-installed. Obviously I shouldn't have
to do that, and it's not really an option on 10 client machines. I've just
tried it on a Windows 98 machine (Office 2K unpatched) with no problems.
Interestingly I thought the Office 2K SR1 had been applied to this machine,
help/about said so. But when I started Speed Ferret yesterday it claimed
that it was an unpatched version of office (which has a bug that can cause
data loss when using SF, they say) even though it says SR1 on help about. In
other words that Office 2K will misreport itself as having the patch, that
it's the actual build number that counts. BUT on the version on Windows 98
help/about reports itself as not being patched. These versions will have
been installed from the same CD (er, one desktop, one laptop, still within
the licence). So how come one version was reporting itself as patched when
SF said it wasn't? Which shouldn't of course matter, I've just patched it
twice. But this is the problem somewhere isn't it. Some dll or olb or
something has got damaged or overwritten and I can't get it back.
TIA, Mike MacSween