
Trim() function in query can't be run in Access Runtime Environment
While Joe's answer is 100% correct when you're dealing with people who have
Access installed on their machine, unfortunately you can't use this approach
with runtime versions of Access (nor, for that matter, with .MDEs, even if
Access is installed)
Recognize that each reference points to a specific file in a specific
location on the development machine. You must be able to resolve each of the
references on the client machine as well. If any of those files are missing
on the client machine, or are in a different location, or are a different
version (or there are differences with any dependencies the files may have),
you'll run into the problem you're having.
Since you can't go into the application on the client machine to fix the
problem (as a result of not being able to make changes with the Runtime
version), you have to work externally to ensure that everything's the same.
Fortunately, Tony Toews has written a free OCX/DLL Version Checker that
should help you in your investigations. You can download it from
http://www.granite.ab.ca/access/ocxdllversionchecker.htm
--
Doug Steele, Microsoft Access MVP
Beer, Wine and Database Programming. What could be better?
Visit "Doug Steele's Beer and Programming Emporium"
http://I.Am/DougSteele/
Quote:
> It is a Reference problem on the other PC.
> They probably have mDAC 2.5 installed.
> Open a module and uncheck the DAO reference. Close the reference window.
> Re-open it and re-check DAO.
> Now try it.
> --
> Joe
> Access MVP
> Check out Dev Ashish's web site for answers to common questions
> http://www.mvps.org/access/
> > Dear all developer:
> > I got the following problem:
> > I design a query like the following that will use the function Trim() to
> > return value from a field:
> > Eg. Select client_no, trim(client_name) from client
> > It's work fine if my computer already installed Access97
> > But when this query was run in the Access Runtime Environment, a error
> > message will be displayed.
> > I also find that others function like left(), rihgt and mid() also got
the
> > same problem when it run in query.
> > if the above function run in a form, it work fine.
> > Many thanks! : )