Hello guys (and girls)
VBA (Access 2003) - XP clients
I've written an app that using the line ...
Set oDom = CreateObject("msxml2.domdocument.4.0")
... and it works fine on 99% of my clients.
I have one XP client that fails on this line with ...
429 ActiveX component can't create object
... i'm utterly baffled as to why this machine should fail. It's XP - it's been kicking around a little longer than the others, but has Office 2003 installed.
Got any idea where I should be looking ? ... like I said, works fine on about 50 machines, this 1 machine fails ... i've checked 'References' and can't see anything missing ... I thought it was a standard reference.
Don't know what else to update ...
... I might try a resinstall of Office, I guess *hmmmm*