It doesn't take an Enigma machine to decrypt the error message, just a trip
to www.cpearson.com/Excel/FormatMessage.aspx. That page has some VBA code
that wraps up the API functions to get the system-defined error text for a
Windows API error number (Err.LastDLLError, not Err.Number).

Unfortunately, this particular error number is like a VBA 1004 -- it
indicates only that *something* went wrong with no clue as to *what* went
wrong. The system text for this error number is "Unspecified error". You'd
think that MS would give better, more meaningful error numbers, none of this
generic crap. An error is a Long, so you have 4 billion different values.
They could have assigned a unique error number of every single line of code
in all of Windows and still have items left over.


--
Cordially,
Chip Pearson
Microsoft MVP - Excel, 10 Years
Pearson Software Consulting
www.cpearson.com
(email on the web site)



"Peo Sjoblom" wrote in message
...
LOL! Do you really want any help with this? Don't you think it would be
prudent to be a bit more forthcoming in what caused this error to appear
etc? We should bring back the people that created the Enigma to decrypt
these messages.

--


Regards,


Peo Sjoblom


"Itzik" wrote in message
...
Hi,
How do I solve this Error ?