reference problem A2K2

[david epsom dot com dot au]

A colleague claims that his Access XP application does not work, on the same
computer, after conversion to an MDE.

His description suggests a references problem: error and failure on any code
at startup.

Are there an suggestions?

(david)

 

[Arvin Meyer]

I know of no way to fix references on an MDE. Have him recompile the
original MDB after removing any unnecessary references, or better still,
build a new MDB file and set only the required references, then compact and
compile and make an MDE.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access

 

[david epsom dot com dot au]

Arvin. The application runs OK as an MDB.
As an MDE ON THE SAME MACHINE, it fails in a manner
that looks like a reference problem. The PC has
2000,2002,2003 installed. The MDE is built in A2002.

(david)

 

[Arvin Meyer]

The only chance I think that you have is to painstakingly add the forms,
reports, and code a few at a time, making new MDEs, until you find the
culprit. I don't envy your task.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access

 

[Brendan Reynolds]

Add half of them. If there is one problem, it is either in that half, or in
the other half. Now ignore the half that doesn't exhibit the problem, and
split the problem half in two again.

I believe there's a technical term for the technique I'm suggesting - binary
search, something like that? Keep splitting the target to be searched into
two until there's only one left.

Of course, when I tried this with some problem data the other day, it turned
out there was not one problem record, but several, and they were
more-or-less evenly distributed! :-( But it does work sometimes.