I downloaded and installed VB HTML Maker - it looks like the way to get Excel VBA code into MS Word with the colors intact. I run Excel 2003 under WinXP Pro SP2 and all updates.
However, when the xla is run it fails on Error 48. I assume the DLL in question is User32, which is cited in a private function declaration. The VBE debugger flags ".CommandBars" in Public Sub Initialize(). I can't find anything in VBA equivalent to LoadLibrary in VB that would provide an error code with more specific info about the reason for the failure.
I notice that the unzipped .xla file is dated 09/15/2007. User32.dll, on the other hand, is dated 03/08/2007, suggesting that it has been updated in one of Microsoft's many WinXP patches. Could this version of user32 be incompatible with VBHTMLMaker.xla? If so, where can a compatible older version of user32 be obtained?
What other possible explanations might there be for the Error 48 failure, and how can I deal with them?
Would appreciate any suggestions or words of wisdom.
However, when the xla is run it fails on Error 48. I assume the DLL in question is User32, which is cited in a private function declaration. The VBE debugger flags ".CommandBars" in Public Sub Initialize(). I can't find anything in VBA equivalent to LoadLibrary in VB that would provide an error code with more specific info about the reason for the failure.
I notice that the unzipped .xla file is dated 09/15/2007. User32.dll, on the other hand, is dated 03/08/2007, suggesting that it has been updated in one of Microsoft's many WinXP patches. Could this version of user32 be incompatible with VBHTMLMaker.xla? If so, where can a compatible older version of user32 be obtained?
What other possible explanations might there be for the Error 48 failure, and how can I deal with them?
Would appreciate any suggestions or words of wisdom.
