OWC10.dll missing/broken... but I don't believe so.
in [General]
|
From: Zen on 3 Nov 2009 12:09 Hey all, I'm experiencing a frustrating problem with access on 2 out of 4 computers, literally all of a sudden. Here's the scoop. 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. So basically my front end file will not work at all. I'm really stumped and frustrated here. Because to me there doesn't seem to be any real reason why this would just start happening on two computers, and one especially where nothing new had been installed etc.
From: Rudolf Lamour on 3 Nov 2009 14:49 "Zen" <r-> schrieb im Newsbeitrag news:%23Iw9phKXKHA.3696(a)TK2MSFTNGP02.phx.gbl... > Hey all, > I'm experiencing a frustrating problem with access on 2 out of 4 > computers, literally all of a sudden. Here's the scoop. > > 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. > > So basically my front end file will not work at all. > I'm really stumped and frustrated here. Because to me there doesn't seem > to be any real reason why this would just start happening on two > computers, and one especially where nothing new had been installed etc. > >
From: Tony Toews [MVP] on 3 Nov 2009 16:00 "Zen" <r-> wrote: >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. <snip> >So basically my front end file will not work at all. >I'm really stumped and frustrated here. Because to me there doesn't seem to >be any real reason why this would just start happening on two computers, and >one especially where nothing new had been installed etc. For unknown reasons converting Access from one version to a newer version inserts this reference automatically. Hmm, probably A97 to A2000 IIRC. 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 Tony -- Tony Toews, Microsoft Access MVP Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ For a free, convenient utility to keep your users FEs and other files updated see http://www.autofeupdater.com/ Granite Fleet Manager http://www.granitefleet.com/
From: Zen on 3 Nov 2009 16:23 Tony thanks for the reply. First lemme add that the developer insists they used 2002 for the new changes. 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? > > For unknown reasons converting Access from one version to a newer > version inserts this reference automatically. Hmm, probably A97 to > A2000 IIRC. > > 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 > > Tony > -- > Tony Toews, Microsoft Access MVP > Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm > Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ > For a free, convenient utility to keep your users FEs and other files > updated see http://www.autofeupdater.com/ > Granite Fleet Manager http://www.granitefleet.com/
From: Zen on 3 Nov 2009 16:36
Also, how do I run that code you provided? 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 End Sub |