Re: Perl & Win32

This is possibly not really a Perl problem at all - as you can see - it appears to be a problem with the regional settings in Excel as described in these articles at MSDN.

Update: It is likely that Re: Perl & Win32 is the actual reason behind this - the error number seems to be some generic Excel automation error.

/J\

Comment on Re: Perl & Win32

Replies are listed 'Best First'.
Re^2: Perl & Win32 by bart (Canon) on Mar 18, 2005 at 11:43 UTC
The "Perl problem" is, IMO, turning these obscure Win32::OLE error messages into something far more informative.	[reply]
Re^3: Perl & Win32 by spurperl (Priest) on Mar 18, 2005 at 11:53 UTC
It would be difficult since errors of this kind are tunneled directly from the OLE engine. It's OLE's cryptic messages that should be fixed - then Win32::OLE will be fine.	[reply]
Re^4: Perl & Win32 by gellyfish (Monsignor) on Mar 18, 2005 at 12:13 UTC
Worse than that, judicious grepping of all of the Windows include files would suggest that this value is not even known to the OLE subsystem but comes from the Application, so without some gigantic registry of the possible `HRESULT` from every possible automation component you are always going to have this problem. /J\	[reply] [d/l]
Re^4: Perl & Win32 by bart (Canon) on Mar 18, 2005 at 12:12 UTC
I figure that there must be a way to ask the system, though OLE, what these cryptic error messages mean, something similar to the API call `GetLastError()` and the libwin32 functions `Win32::GetLastError()` and `Win32::FormatMessage()`. In that case, I think it's reasonable to ask Win32::OLE to handle the necessary paperwork for us.	[reply]