Function not available in expression error

[Sniper-BoOyA-]

Good morning,

I have got a problem on one of our computers.

We use Microsoft Access databases to enter test data and eventually generate reports.

On 1 computers i get the following error when opening the report:

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

I figured this is a reference problem so the next thing i did was to pinpoint what reference was causing this error.

It turns out it is the Microsoft DAO 3.6 Object Library. Simply removing the reference and adding it again fixes it and allows you to open reports just fine.

The problem is though, this message comes back every now and then. Which is getting annoying and the person who is making the reports is about to throw his computer out of the window.

I was wondering, have any of you guys experienced anything like this before, and what did you do to solve this?

 

[Rx_]

http://support.microsoft.com/kb/194374
Does this sound like the problem?

Question: was the database developed in a previous version of Access? Then opened to run in a new version of Access?
Opening an older developed version of Access with a newer one can cause different types of problems.

This is my suggestion either way.
Create a blank version of Access (latest version).
Migrate all objects over from the running version to the new blank version.
Go and reset up the startup form and other features.

This is something useful to do on say a quarterly basis anyway. It gets rid of any broken links, super compresses the data, re-indexes tables and more.
Never open an older version of Access with a new version. This "update" process is discussed in other places in this forum.

Please let us know if this works. There will likely be others who search on this problem in the future.

 

[Sniper-BoOyA-]

Good morning Rx,

Thanks for the information.

To answer your question No, the database was developed in the same version of Access (2003).

But, i will try the steps you suggested anyhow.

The thing that makes me wonder the most is the fact that this error only pops up on 2 computers. Because we use this database on 8 computers in total.