#Name?

I have a client who has installed an access xp database using the access
runtime. I have a report in the database that uses the trim function. On
her machine (windows xp home edition sp2) it gives the #name?
instead of the data. On my machine it works just fine. What could be the
problem and how do I solve it since she is using the mde.

She is missing one of the references that you have in your database. The
runtime that you packaged may not have included all the libraries that are
needed.

--

Ken Snell
MS ACCESS MVP

"Dale Brown" wrote in message
...
I have a client who has installed an access xp database using the access
runtime. I have a report in the database that uses the trim function. On
her machine (windows xp home edition sp2) it gives the #name? instead of
the data. On my machine it works just fine. What could be the problem and
how do I solve it since she is using the mde.

Is there any easy way to find out what she is missing without send the
..mdb file and checking what comes up with a missing reference?

Ken Snell [MVP] wrote:
She is missing one of the references that you have in your database. The
runtime that you packaged may not have included all the libraries that are
needed.

Not that I know about... that doesn't mean that there isn't a way, but I am
not aware of one.

However, I don't think you should need to do that. Your packaging of the
runtime is where the references get set up. Check the mdb file on your end
and be sure that you're including all required references when you create
the runtime.
--

Ken Snell
MS ACCESS MVP


"Dale Brown" wrote in message
...
Is there any easy way to find out what she is missing without send the
.mdb file and checking what comes up with a missing reference?

Ken Snell [MVP] wrote:
She is missing one of the references that you have in your database. The
runtime that you packaged may not have included all the libraries that
are needed.

Ken,

I sent her an mde that had a form that did the reference check based on
the code from this article http://support.microsoft.com/kb/209849/EN-US/
and it did not show any missing. Based on the references on my machine
hers was missing the reference for
c:\program files\common files\microsoft shared\web components\10\owc10.dll

Would this dll be causing the Trim function to not work properly. If so
how do I get her to have the reference. In my package wizard I had
chosen the option to include the Access Runtime and the include system
files. I did not check the install internet explorer 5.1 since I know
she has a newer computer and should have a newer version than that
already on it. Did I miss something.

Dale

Ken Snell [MVP] wrote:

Not that I know about... that doesn't mean that there isn't a way, but I am
not aware of one.

However, I don't think you should need to do that. Your packaging of the
runtime is where the references get set up. Check the mdb file on your end
and be sure that you're including all required references when you create
the runtime.

Office Web Components library (owc) is not needed for your database unless
you plan to use HTML, Data Access Pages, or other browser-type objects. I
would uncheck it from your references if you're not using it.

Otherwise, she can download owc from Microsoft's Office site. It's available
for any as a download.
--

Ken Snell
MS ACCESS MVP



"Dale Brown" wrote in message
...
Ken,

I sent her an mde that had a form that did the reference check based on
the code from this article http://support.microsoft.com/kb/209849/EN-US/
and it did not show any missing. Based on the references on my machine
hers was missing the reference for
c:\program files\common files\microsoft shared\web components\10\owc10.dll

Would this dll be causing the Trim function to not work properly. If so
how do I get her to have the reference. In my package wizard I had chosen
the option to include the Access Runtime and the include system files. I
did not check the install internet explorer 5.1 since I know she has a
newer computer and should have a newer version than that already on it.
Did I miss something.

Dale

Ken Snell [MVP] wrote:

Not that I know about... that doesn't mean that there isn't a way, but I
am not aware of one.

However, I don't think you should need to do that. Your packaging of the
runtime is where the references get set up. Check the mdb file on your
end and be sure that you're including all required references when you
create the runtime.