When I see this type of behavior - one computer the program works, another it
fails - I suspect there is a library references problem.
To do its job, Access makes use of various external program and object
libraries. If you move a database from one machine to another, these
references may be "broken".
When this happens, you need to take steps to let Access repair the
reference(s) ON THE COMPUTER WHERE THE FAILURE IS OCCURRING.
This is going to be particularly tough to solve if you are using RUNTIME since
you won't be able to get to the references screen.
You might be able to use the following (Never tested), but it will have to
execute on startup
Sub EnumerateReferences()
Dim ref As Reference
Dim strOut As String
For Each ref In Access.References
strOut = strOut & vbCrLf &_
ref.Name & IIf(ref.IsBroken, " Missing", " OK") & _
vbCrLf & ref.FullPath & vbCrLf
Next ref
MsgBox strOut
End Sub
If you can temporarily install a full version of Access on a computer where
this is failing the following may help.
Here are MVP Doug Steele's instructions for how to do it:
*** Quote ***
Any time functions that previously worked suddenly don't, the first thing to
suspect is a references problem.
This can be caused by differences in either the location or file version of
certain files between the machine where the application was developed, and
where it's being run (or the file missing completely from the target machine).
Such differences are common when new software is installed.
On the machine(s) where it's not working, open any code module (or open the
Debug Window, using Ctrl-G, provided you haven't selected the "keep debug
window on top" option). Select Tools | References from the menu bar. Examine
all of the selected references.
If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you just
unselected (you can tell by doing a Compile All Modules), go back in and
reselect them.
If none have "MISSING:", select an additional reference at random, back out of
the dialog, then go back in and unselect the reference you just added. If that
doesn't solve the problem, try to unselect as many of the selected references
as you can (Access may not let you unselect them all), back out of the dialog,
then go back in and reselect the references you just unselected. (NOTE: write
down what the references are before you delete them, because they'll be in a
different order when you go back in)
For far more than you could ever want to know about this problem, check out
http://www.accessmvp.com/djsteele/Ac...nceErrors.html
Just so you know: the problem will occur even if the library that contains the
specific function that's failing doesn't have a problem.
**** End Quote ****
John Spencer
Access MVP 2002-2005, 2007-2010
The Hilltop Institute
University of Maryland Baltimore County
rce7144 wrote:
> I have an Access 2007 solution I created a year or so ago and all was
> working fine. The final solution uses access runtime and an accde
> file. The customer requested some revisions to the solution a few
> months ago. After I made the revisions I reinstalled the solution on
> the original workstations and also installed it on a few other
> computers as well. For some reason, the original workstations do not
> open a form correctly. But on the computers that have never run the
> original solution, everything works fine. The problem is when a form
> is opened from the switch board or a search macro, the form is
> blank ... there are no fields, no text, no data ... nothing, just a
> blank form showing the form background color. This only happens on the
> computers that had the original solution installed. I tried
> uninstalling runtime, as well as the original application. I
> reinstalled it with the latest access runtime. But still no luck.
>
> Any help would be appreciated.
Similar Threads
