Reference error when opening db in another pc

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

spacerocket - 11 Aug 2005 08:04 GMT

I recently created a database and placed it in a shared drive for other users
to use. I tested opening the db from my computer and it works fine. However,
when the database is opened by another computer, it displays this error msg:

-------------------
Your database or project contains a missing or broken reference to the file
'SgCalendar.ocx' version 1.0.

* To ensure that your database or project works properly, you must fix this
reference.
-------------------

The debugger window will be displayed whenever a report with any date
formatting is run. I've tried to update the other computer to SP1 since I am
using SP1. But the error message still appears. What else should I do? Pls
advise!

Reply to this Message

Nikos Yannacopoulos - 11 Aug 2005 08:35 GMT

Find the SgCalendar.ocx file on your HDD (chances are it is either in
C:\Windows\system32 or somewhere in c:\Program Files). Copy it on the
other users' PC's, in the corresponding folder, then open Access (and
any database) and go Tools > ActiveX Controls; click Register, browse to
the .ocx file, select it and click OK. The job is done.

Note: if this is an ActiveX control that came with some software you
purchased (other than MS-Office or Access), then there is probably a
licencing issue involved!

HTH,
Nikos

Reply to this Message

Tony Toews - 11 Aug 2005 19:25 GMT

>I recently created a database and placed it in a shared drive for other users
>to use. I tested opening the db from my computer and it works fine. However,
[quoted text clipped - 6 lines]
>* To ensure that your database or project works properly, you must fix this
>reference.

Are you using this OCX anywhere?

Do you have any references besides the basic three? Are you sure you
need them? Write down the path and name of the extra ones, delete
from the references list and Compile and Save All. Keep any
necessary references and ensure they are distributed to the target
system.

For a very detailed page on reference problems see
http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html

Ctrl+G will take you into the Debug/Immediate window. Then click on
Tools on the menu bar and References.

The Access 97 default references are:
Visual Basic for Applications
Microsoft Access 8.0 Object Library
Microsoft DAO 3.5x Object Library

The Access 2000 default references are:
Visual Basic for Applications
Microsoft Access 9.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.1 Library
or
Microsoft DAO 3.6 Object Library

The Access 2002 default references when the MDB is created in Access
2000 format are:
Visual Basic for Applications
Microsoft Access 10.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.1 Library

The Access 2002 default references when the MDB is created in Access
2002 format are:
Visual Basic for Applications
Microsoft Access 10.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.5 Library.

The Access 2003 default references when the MDB is in A2000 format are
Visual Basic for Applications
Microsoft Access 11.0 Object Library
OLE Automation
Microsoft DAO 3.6 Object Library
Microsoft ActiveX Data Objects 2.1 Library

The Access 2003 default references when the MDB is in A2002/A2003
format are
Visual Basic for Applications
Microsoft Access 11.0 Object Library
OLE Automation
Microsoft DAO 3.6 Object Library
Microsoft ActiveX Data Objects 2.5 Library

Tony

Signature

Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

Reply to this Message

spacerocket - 23 Aug 2005 03:20 GMT

Dear all,

Thanks for your replies. I've finally found out that the error is caused by
the VB Reference. I have Palm installed on my PC (which I suspect uses this
file) and I unticked it in the Reference list.

Reply to this Message