• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 773
  • Last Modified:

Access 2010 Function not available error

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.
0
TownTalk
Asked:
TownTalk
  • 2
  • 2
2 Solutions
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<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.
0
 
peter57rCommented:
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.



0
 
TownTalkAuthor Commented:
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?

0
 
TownTalkAuthor Commented:
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.
0
 
peter57rCommented:
You can run this to get the full paths..

Sub listrefs()
Dim rf As Reference
For Each rf In Application.References
Debug.Print rf.FullPath

Next rf

End Sub
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now