To keep pace with competitors, businesses must keep employees productive, and that means providing them with the latest technology. This document provides the tips and tricks you need to help you migrate an outdated PC fleet to new desktops, laptops, and tablets.
COURSE of the MONTH
14 days, 8 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Access 2010 Function not available error
Posted on 2011-03-10
This is a database application that I recently updated from Access 2000 to Access 2010.
I'm got the retail version of Access installed on our 64 bit 2008 server and from there i'm publishing the .ACCDE file to distribute to the client pc's.
Since I did the upgrade from Access 2000, the client programs are throwing up an error:
Function is not available in query expression left$(..........
On the server i am not getting any error.
One of the clients has also got the retail version of 2010. If he opens the .ACCDB and publishes the .ACCDE then there is also no error. So the only time the error occurs is when a client opens the .ACCDE which was published from the server.
Edit: I've just been told that when the clients use a .accde file that was compiled on the 32bit client, it runs much faster
Is this a 32/64 bit issue? Or is there another reason? Before anyone asks, I've imported all the objects into a fresh .accdb and still got the same problem.
I'm got the retail version of Access installed on our 64 bit 2008 server and from there i'm publishing the .ACCDE file to distribute to the client pc's.
Since I did the upgrade from Access 2000, the client programs are throwing up an error:
Function is not available in query expression left$(..........
On the server i am not getting any error.
One of the clients has also got the retail version of 2010. If he opens the .ACCDB and publishes the .ACCDE then there is also no error. So the only time the error occurs is when a client opens the .ACCDE which was published from the server.
Edit: I've just been told that when the clients use a .accde file that was compiled on the 32bit client, it runs much faster
Is this a 32/64 bit issue? Or is there another reason? Before anyone asks, I've imported all the objects into a fresh .accdb and still got the same problem.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2-
2
5 Comments
Active today
<<I'm got the retail version of Access installed on our 64 bit 2008 server and from there i'm publishing the .ACCDE file to distribute to the client pc's.>>
Did you install the 32bit version of Office or 64? 64 won't fly if they have 32bit OS's.
<<Function is not available in query expression left$(..........>>
This is a clear sign that the VBA references are broken.
Something in your reference list is not the same as it is on the target computer. Have them open the app with the shift key held down. Once there in, have them do a Alt/F11 to bring up the VBA code window. Click tools/references and look for any that are listed as MISSING or BROKEN.
JimD.
Did you install the 32bit version of Office or 64? 64 won't fly if they have 32bit OS's.
<<Function is not available in query expression left$(..........>>
This is a clear sign that the VBA references are broken.
Something in your reference list is not the same as it is on the target computer. Have them open the app with the shift key held down. Once there in, have them do a Alt/F11 to bring up the VBA code window. Click tools/references and look for any that are listed as MISSING or BROKEN.
JimD.
The problem is that your config does not match your customer's and when you create a mde/accde file the paths to object libraries are hard code to the paths on the machine where the mde/accde is created.
It's a 32/64 bit issue in that the paths for 32bit apps running on 64bit windows are all different to the paths on 32bit windows.
I think you will have to consider issuing an accdb file to overcome this.
It's a 32/64 bit issue in that the paths for 32bit apps running on 64bit windows are all different to the paths on 32bit windows.
I think you will have to consider issuing an accdb file to overcome this.
It's the 32 bit version of Access I installed on the server. When the client pc openend the .accdb for the first time, it sat there for a moment saying that it was looking for MSADOX.DLL, but eventually when it loaded I checked the references and everything was correctly referenced.
I can see now that on the server, the path for several of the references starts off C:\Program Files (x86)\......
So obviously the clients will not see this path. So I hit on the idea of putting a copy of all the relevent library files on the network share where the database back end is stored, and referencing them from there. Unfortunately, when I try to look at the file names in the references dialog box, the path names are too long and I cant see the name of the actual file.
Is there a way I can find out the filenames involved?
I can see now that on the server, the path for several of the references starts off C:\Program Files (x86)\......
So obviously the clients will not see this path. So I hit on the idea of putting a copy of all the relevent library files on the network share where the database back end is stored, and referencing them from there. Unfortunately, when I try to look at the file names in the references dialog box, the path names are too long and I cant see the name of the actual file.
Is there a way I can find out the filenames involved?
I could see some of the shorter filepaths. So I placed a copy of the file on the network share. Then I went into Tools -> references and tried to browse to it. I was surprised to see that it snaps back to the original location whenever I try to change it.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
As tax season makes its return, so does the increase in cyber crime and tax refund phishing that comes with it
In Part II of this series, I will discuss how to identify all open instances of Excel and enumerate the workbooks, spreadsheets, and named ranges within each of those instances.
In Microsoft Access, learn how to “cascade” or have the displayed data of one combo control depend upon what’s entered in another.
Base the dependent combo on a query for its row source:
Add a reference to the first combo on the form as criteria i…
In Microsoft Access, learn different ways of passing a string value within a string argument. Also learn what a “Type Mis-match” error is about.
Suggested Courses
Course of the Month14 days, 8 hours left to enroll
770 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.