Left Function is not available in expressions in query expression (Access 2000)

This is recently occuring in some offsite computers using a variety of operating systems (95, 98, 2000, and possibly XP).

The Access 2000 database contains a query that uses the Left() function and recieving the error:

"Function is not available in expressions in query expression 'Left(.." etc.

From the information I have gathered about this problem so far, I believe from what I read, please someone correct me if I am wrong.. that.. the development computer is using an earlier version of the .dll that contains the Left() function while the user computers off-site have gotten ahold of a newer version of this same .dll.

I have not been able to locate which .dll file contains the function Left(). Does anyone know which .dll it is? Maybe I can get a good start from there of how to tackle this problem and work from there.

I have found an article and a solution that involved refreshing the references. This will not work in this instance due to the non-dev databases being .mde.

Thank you for any possible help,

Paul
AlderAsked:
Who is Participating?
 
NetminderCommented:
Per recommendation, points refunded and question closed.

Netminder
CS Moderator
0
 
nico5038Commented:
Normally this points to missing references.
Open a module and select Tools/References
When you see a checked library starting with "MISSING" then uncheck this one and (when necessary) replace with another version.

Nic;o)
0
 
jrigginCommented:
The 'left' function is in VBE6.DLL (Usually C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6.DLL) - I have version 6.0.89.67 w/ Access 2000

For '97, it is in  C:\Program Files\Common Files\Microsoft Shared\VBA\VBA332.DLL.  I have 3.0.0.7019 for Access 97.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
Mach1proCommented:
The dll that contains the functions don't have to be the ones missing to come up with the error.  I recently added a runtime app to a Win2000 PC and the file that was missing causing the Left function not to work was  VBEEXT1.ole.
I've also run into situations where a different version of the CommonDialogue file on a PC would generate DateFunction errors.  The best bet is to to look at the references that are on the PC that is working and then make sure that the same references exist and are registered on the PC that isn't working.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
Paul,

<<I have found an article and a solution that involved refreshing the references. This will not work in this instance due to the non-dev databases being .mde.>>

That's one of the big headaches with MDEs; you can't fix broken references.

You need to ensure that all .DLLs are the same as those on the development machine and appear some where in the path.  Many times references break simply because a DLL is in a different location or is a different version.

One way around this is to ensure that your development machine and those that you distributing to are up to the same rev levels or better yet, distribute a setup package rather then passing around just a copy of the MDE.

Jim.
0
 
jrigginCommented:
Jim is right about useing a setup package, but you need the development kit to make those.  The last time I used them was with '95, and they only did a correct install on about 80% of the machines. Maybe they improved it.

But, the dlls do not need be in the same path on the target machine.  If the dll is registered on the client, its location does not matter - it will be pointed to the right location by the registry entry.

You can check your dependancies with depends.exe which you can get from http://www.microsoft.com/msj/defaultframe.asp?page=/msj/code/depends.htm&nav=/msj/code/newnav.htm

This will tell you what is missing on the client machine.
0
 
AlderAuthor Commented:
Found what was causing the problem. Microsoft DataGrid Control 6.0 had been added to the references by accident and the control's file had not been distributed to the offsite computers. Somehow this reference without a file to reference caused the problem with the Left() function when used within a query.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
Good work!
Jim.
0
 
AlderAuthor Commented:
All comments have been very helpful for me to get to the root of the problem. I do not know which comment to select as the answer.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
I don't think any. You pretty much figured it out on your own.

If you feel anyone was somewhat helpfull, how about deleting this question and posting a 50 point "thank you" type questions.

Jim.



0
 
nico5038Commented:

No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in Community Support that this question is:
 - PAQ'd and pts refunded
Please leave any comments here within the
next seven days.

PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER !

Nic;o)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.