4 office computers with XP Pro and Office 2002. We just made a change to our
front end mdb so we could push some invoices to quickbooks.

I went ahead and opened the front end on two computers, everything appeared
to work normally it asked to find the backend db and did a little conversion
to add some new tables and then loaded our switchboard home screen.

The backend is shared on the network so actually I went ahead and just
copied the front end from the 2nd computer (since it had already changed the
path of the backend tables) to computers 3 and 4.

This is where it got interesting... and by interesting I mean completely
frustrating.

Basically when I opened the front end on computers 3 and 4 I would get an
error about OWC10.dll (ver 1.2) being missing/broken reference. After
clicking ok there was another warning window.
Compile error;
Can't find project or library.

When I click okay on that, the vb editor loads up with various modules etc.
and only one of the modules has any code highlighted in yellow, just one
line.
"Public Function GetBackEndPath() As String"

Anyway this happened on computers 3 and 4. Computer 4 recently had a new
version of quickbooks installed but computer 3 had nothing new installed in
a quite a while.

I tried using our old front end but then I got the same exact problem on the
old front end too!

In the past we used to use a runtime version of our front end so I made an
executable that would exctract the dll and run a batch script to copy the
dll to the proper locations and reg it.
http://www.buggyonpurpose.com/random/owc10batch.txt

So besides trying to rereg that DLL, I have also tried to repair install
access,

UNINSTALL/reboot and reinstall office completely

At this point I I no longer get the initial nag window about missing or
broken reference but I still get the
Compile error;
Can't find project or library.

"Zen" <r-> schrieb im Newsbeitrag
news:%23Iw9phKXKHA.3696@TK2MSFTNGP02.phx.gbl...

Remove the reference and compile your project. If it compiles you
didn't need the reference.

Also run the following code and report back.  If there are any other
potential problems we'll warn you about them.

Sub ViewReferenceDetails()

Dim ref As Reference

    For Each ref In Access.References
        Debug.Print ref.Name & " - " & ref.Major & "." & ref.Minor & "
- " & ref.FullPath
    Next ref

End Sub

However, with that said. Even if they used a newer version,  my OLD front
end should still work

So now bear with me because I don't understand what you mean when you say
compile my project. The front end is not an executable runtime, outside of
that what is there to compile?

I launched the front end using Shift Enter so it wouldn't give me any of
those errors. Then I pressed f11 and created a new modele by copy and
pasting the code

But double clicking the module just loads the editor. If I click the run/sub
user form button on the vb editor nothing seems to happen, same if I to to
Run>Run Sub/User Form or hitting F5

Sub ViewReferenceDetails()

Dim ref As Reference

    For Each ref In Access.References
        Debug.Print ref.Name & " - " & ref.Major & "." & ref.Minor &
"spaceMINUSspace" & ref.FullPath
    Next ref

I can only see parts of this thread so not sure if this has been tried
but...

1. Open the database by holding down the shift key
2. Go to any module (code window)
3. Select Tools then select References
4. When that window opens FIRST uncheck anything that says MISSING before
it's name then...
5. Write down all the ones you see with any check marks next to them, they
should all be at the top, and post them here...

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

The ONLY  missing one is Microsoft Office Web Components.
As I mentioned previously I have this dll and a script to register it.
However I just downloaded the installer from
http://www.microsoft.com/downloads/details.aspx?FamilyID=982b0359-0a8...

First I tried reinstall (at the end it said it was installed/repaired
successfully) but I still got the missing reference in my database.
So I uninstalled and rebooted and then tried a reinstall.
Even after reinstalling it still shows missing reference.

For testing sake I unchecked the missing reference closed and relaunched the
front end, everything appeared to work fine. So I have to contact my
original developer to see if there is going to be a problem by removing the
reference...

As I said, I can only see parts of this thread in my newsreader so not sure
what has been mentioned before.  Sorry, if I repeat some on the questions
asked and answered.  Now, on to your issue...  I do not believe you need
that reference as you have found out.  It should also be noted that going
forward you will not be able to use it Access 2007.
--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

Call ViewReferenceDetails

in the immediate window.

ERROR WINDOW
Run-time error '-2147319779 (8002801d)':
Your contacts database or project contains a missing or broken reference to
the file 'OWC10.dll' version 1.2

Also, if I remove the reference and then try to compile the window flashes
briefly and nothing happens.

Let me add, that this is a really old project that has been updated and
revised since 1999 originaly with access 97 or 98 then upgraded to 2000 and
then we've been using XP (2002) ever since.

Our core developer last used ver 2003 if I remember and it's likely he put
this reference, not the guys who made these most recent changes.

But I haven't been able to get a hold of him about it.

"Tony Toews [MVP]" <tto...@telusplanet.net> wrote in message
news:jtt3f51ula2u7tnaivvfi4cripifd7json@4ax.com...

Tony thanks for the suggestion.

Will post back if I find out more.
"John W. Vinson" <jvinson@STOP_SPAM.WysardOfInfo.com> wrote in message
news:5534f5hr2c6vml061508qbjh3snqqra3cb@4ax.com...

As the user of the app, you shouldn't have to mess around with this.
The developer should have taken better care with the references.

I would say that the list of references indicates a developer who is
barely competent, as several of the references are problematic for a
number of reasons. Competent Access developers endeavor to keep
references to a minimum precisely because there are so many
circumstances that can break them. Any app with more than the three
base references (Access, VBA, DAO) is an app that I'm suspicious of,
as it indicates a developer who isn't planning ahead, or is just not
at a level of competence that is appropriate for someone being paid
as an Access developer.

Harsh, but it's the way I see it.