Function not avail error???

Casperov

Registered User.
Local time
Today, 07:30
Joined
Nov 15, 2004
Messages
18
Hello,

I have created an Access system and released attempted to run it on another pc. However, when a specific query is run, I am getting the error message "Function is not available in expressions in query expression 'LTrim([tblF006.Business Unit])'."

Does anyone know why this is happening on the test machine but no mine?

Thanks,
casperov :eek:
 
Yes the test machine is missing a reference that is used on your developement machine. If you go to any coding window on the new machine and then go to Tools menu and then References there will probably be something in the top of the list that is missing. It may just be a version issue. Scroll through the rest of the list to see if the test machine has a comprable version on it.
 
I cannot at the moment check the references, since I am remoting the test pc. However, if the references don't match, how would I get them in sync?

Thanks for you help,
casperov :)
 
references are the same

Okay,

I created a new module and it allowed me access to the references...but they are the same.

What should I check next?

Thanks,
casperov
 
'LTrim([tblF006.Business Unit]) is a very basic part of VBA. When a reference is not right the VBA reacts by not allowing event he most basic of code to operate.

You have to have a reference that is not correct
 
There are times when nothing is marked MISSING. You can force the references collection to be refreshed by checking or unchecking any reference.
 
refs

Hi Pat,

There have been other suggestions regarding the references. However, if I am installing a runtime version of Access 2002, how do I ensure that the references are all up to date?

Do I download all the updates and service packs for Access on my pc before I create the runtime package?

Thanks,
casperov :rolleyes:
 
You can add startup code that verifies that the references are intact. I downloaded an example some time ago but never tried it. It is too large to post but if you send me a PM with your email address, I'll email it to you. You can also search the kb and msdn which have articles with sample code.
 
It's Working!!!!

Okay,

So what I realized that caused my reference issues was the fact that I imported from an older system to a new version of Access. So I took the query that wasn't working and created a new database in Access 2002. What do you know...they query worked. So I checked the refs and deleted the 7 or 8 refs in my non-working project and only checked the refs that were checed in the newly created database.

Woll-ah!!! it worked.

I originally had 7/8 refs, but it seems only 4 were required to get my system working. :D

Visual Basic for Applications
MS Access 10.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.1 Library
 
Last edited:
There are times when nothing is marked MISSING. You can force the references collection to be refreshed by checking or unchecking any reference.

I have just had one of those times and was at my wits end trying to find the problem when nothing was shown as missing. This advice from nearly fifteen years ago has just enabled me to get a quick resolution (once I found the post) to another one of those delightful advances provided by Windows 10 in undermining the operation of legacy (or, for Microsoft, "obsolete") software. I still use Access from Office XP because it does what I need and I no longer have an employer paying for expensive upgrades.

I have just registered purely so I can post a thank you to Pat Hartman (hoping he will see this) and a thank you to Access World Forums for keeping this post current.
 

Users who are viewing this thread

Back
Top Bottom