Broken References

I have an end user whose References keep breaking. I suspect that it's
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/information-technology/13586-broken-references.html
because of occasional updates to his system.

Is there a way to explicitly declare the references? If so, do those
declarations need to be in every form?

Thanks in advance for your help!

*

 
Do share your immediate thoughts or reactions on this issue? We value your views! Login Now! or Sign Up Today! to share your views with us.. Gurfateh!

Peter, it is impratical to try to programmatically fix the references using
code in an Access database where the references are broken. See michka's
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=13586
article:
How to guarantee that references will work in your applications
at:
http://www.trigeminal.com/usenet/usenet026.asp?1033

The most practical solution is to use as few references as possible, so
there are fewer to break. Most databases can be designed to use just 3.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"PeterM" wrote in message
news:966D6053-9C89-46A3-82ED-DB0C8E10055C@microsoft.com...
>I have an end user whose References keep breaking. I suspect that it's
> because of occasional updates to his system.
>
> Is there a way to explicitly declare the references? If so, do those
> declarations need to be in every form?
>
> Thanks in advance for your help!
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=13586

PeterM wrote:

>I have an end user whose References keep breaking. I suspect that it's
>because of occasional updates to his system.

To expand on Allen's reply I suspect you have some extra references
which you don't need but are somehow present on your system but not on
that particular end users system . Or you may be using some OCXs
which aren't on that persons system.

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
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=13586
system.

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

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

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
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=13586
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 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