Needless to point that all Microsoft & Symantec material on the subject is out of date. Office 2003 needs an Online registration procedure.

The call is CreateObject("application.whatever")Err.Descriptio n "Automation Error" & Err.Number"-2147024770 xxxx". Uninstall & reinstall is not a way of solving/understanding problems.

Please relate to the specific problem.

José Maria

Maybe I wasn't too specific.
The problem referred above is well documented concerning previous versions of both Symantec Norton A-V and Microsoft Office.
The thing is to recover the dynamic library that corrupts, which could be the case, if it is the case.

You still have not asked the group a question. What is your question? What is the problem and what do you want solved? All you've done so far is tell us how something is supposed to function.


Greg Serrano
Michigan Dept. of Environmental Quality, Air Quality Division

Thank you.

Application.CreateObject is a common line using Office VBEditor.
(Automation, previously JetEngine)

The err.Num is not very common. Yet, information about this specific err.Description and err.Num has been published both by Microsoft and Symantec (aparently occurs when S.Norton A-V is installed over any Office group of programs).

DLL corruption (oleaut32.dll or others)may be the origin of the err.Ocurrence.

In the end it happens that MS & SYM. information does not result in later versions of both products, and one will have to re-install the two packages.

Making it short, I would like to know if any person in the group, having gone through the same problem, would be willing to share the solution for this error in aproximate conditions, i.e., Office 2003.

Thank you again

I hope Microsoft & Symantec Monsieurs & Madames read following lines.

first:
http://support.microsoft.com/kb/246018
and then:
http://support.microsoft.com/kb/244264/EN-US/

or the other way round.
What all those lines mean is "we don't know".
Removing with regsvr /u a .dll can be an encounter with an endless loop of the same err.message.
Removing oleaut32.dll will certainly result in re-install all.

If this happens to any of you, do not remove oleaut32.dll, just rename it.

Automation, previously Jet Engine is a great way of exchanging data. But if it fails at this level it can cause damage, serious damage.

I certainly need help!!

I wish I did have a solution for this problem.

I had to un-install Office 2003, un-install Norton Internet Security 2005 and re-install the two packages in the following order:

Norton Internet Security

Office 2003

I hated it, but it was the only way to have Automation working.

End of story.

I have found that when I get an error number of a very large negative number, it USUALLY means that I have misspelled something in my call or used a variable for something that doesn't exist. Instead of giving me that exact error message, Access will flash this weird error number instead.

Look closely at your code and make sure every variable is spelled correctly and that every object exists.


Greg Serrano
Michigan Dept. of Environmental Quality, Air Quality Division

Greg, the number is negative because its highest bit is set. The error message in this particular case is

    11111111111111111111111111111111100000000000011100 00000001111110

Separated into bytes, that is

    11111111 11111111 11111111 11111111 10000000 00000111 00000000 01111110

(It is an 8-byte number.)

Large errors are not all that uncommon. In fact, MS recommends that when you are creating custom error (to return from classes, UserDefined Functions, etc, that you use vbObjectError + <your own number, 1, 2, 3, etc.>, like Err.Raise vbObjectError + 1, . . .
vbObjectError equals

    -2147221504
    11111111111111111111111111111111100000000000010000 00000000000000
   (Actually the value is 18446744071562330112, when read as an unsigned integer).

So any error you create according to MS’s standards/recommendations will read as a negative number.

Brian

 Thanks for the education in error codes. I knew they meant something, but had no clue what!

Error codes such as this don't make much bit of sense to the "average" user and if you press the HELP button upon getting the error, I (for one) always get a blank screen. So without any info from Access, I have figured out that when I get this kind of error, it usually means I mispelled something.

Greg Serrano
Michigan Dept. of Environmental Quality, Air Quality Division