Problem Solved !!
The problem resides in the file "TbRun97.xls". This is an
Excel add-in file included in the system by TextBridge
(OCR software).
To solve the issue just move or delete the file from the
folder in which is found (search for it.. it's inside some
Office installation sub-folder).
A little more information about the file can be found
he
http://support.microsoft.com/default.aspx?scid=%
2Fservicedesks%2Fbin%2Fkbsearch.asp%3FArticle%3D27 2066
Thanks to people who read and tried to help me !!
- Humberto -
-----Original Message-----
Is Excel 97 the only version of Excel installed on the
machine. If not, you
need to install the versions from oldest to newest and
put each in a
separate location.
Regards,
Tom Ogilvy
"Humberto" wrote in
message
...
The following has some messages that I translated from
Portuguese, since I don't have the English version of
the
software..
So, some of the words cannot be exactly the same I used
below. I translated the messages/text trying not to
affect
the meaning
of the original contents in English. Sorry if I made
some
mistakes (I'm not that fluent in English since I'm
brazilian)...
I'm receiving the following error message every time I
try
to open the "References" box in VBA (Visual Basic
Editor)
of Excel 97:
"Object library not registered"
The steps are the following:
1) Run Excel97 (new instance - not from an excel
document
file)
2) When Excel97 is already opened, press Alt+F11 (or
click "Tools" "Macro" "Visual Basic Editor" from
Excel97 main menu)
3) In Visual Basic Environment (Visual Basic Editor),
click "Tools" "References".
After this, a message box with title "Microsoft Visual
Basic" and message "Object library not registered" pops
up.
In this message box, there are two buttons ("Ok"
and "Help"). When I click on the "Help" button, the help
referred to the error
is shown. The following text is displayed on the help:
--------------------------------------------------------
---
---------------
"The Visual Basic for Applications object library is no
longer a standalone file; it's integrated into the
dynamic-
link library (DLL).
On previous versions, when you start an application that
used Visual Basic for Applications, some object
libraries
were loaded. This error has the following cause and
solution:
Cause: An attempt to load an older version of the Visual
Basic for Applications object library (vaxxx.olb) or
host
applications object library was made. Although, the
correct version of these object libraries could not be
found in the system registry.
Solution: Register your application again. On Macintosh,
delete the vba.ini file from Macintosh Preferences
folder
and restart your application.
To get more informations, select the item and press F1."
--------------------------------------------------------
---
----------------
I looked for any "va*.olb" file on my machine and found
only "vaen21.olb". I couldn't conclude anything just
with
this...
After searching the whole Internet I found only one
person
who got the same problem described here
(http://www.visualbasicforum.com/showthread.php?
s=1c25f1c4cbb87876e3aabbfccb46ca82&t=58828)...
I did some tests on machines different from mine and
this
problem occured on some machines, and on anothers it
didn't happen (I mean, the "References" box was shown
normally).
I did other experience (uninstalling and installing
Office97) and the results surprised me:
1) Uninstalled Office97 from my computer (choosing
the "Remove" option from the install/uninstall Office
menu).
2) Rebooted the system.
3) I noticed that, even uninstalled, some Office files
(the main Office folder and about 46Mb of files) were
still on the hard disk.
4) Ran excel.exe executable file. A messagebox telling
that the "scanload.dll" file have not found was shown.
5) Clicked "Tools" "Macro" "Visual Basic Editor".
6) The Visual Basic Editor (Environment) opened
normally.
In this editor, I clicked "Tools" "References".
The "References" box was shown without problems !!
After this, I reinstalled Office97 and the problem came
back.
This is for me an evidence that the problem is ocurring
because of some missing file...
I'm using Windows NT4.0 (English) with Service Pack 6
and
Office 97 (Brazilian Edition) with SR1 and SR2 patches
applied (but even not
using these patches the problem used to occur).
Please, I'll be very grateful if you can send me any
information on how to solve this problem.
My email is:
Thanks in advance !!
- Humberto -
.