Solved

WXP Access07 Runtime generates error on Access07 on Vista.

Posted on 2009-05-19
2
258 Views
Last Modified: 2012-05-07
We just had a new database created for us. It was developed on a Windows XP box that was fully updated and patched from Windows Update.

The runtime of that database generates an error on a Vista box also with MS Access 2007. The Vista machine was also fully patched from Windows Update.

The error is:
Function is not available in expressions in query expression 'Left([IngredientX]![LOC],6'.

I looked through the Library References on both machines and there is NOT one that indicates "MISSING". I did a line by line comparison on each machine and did find a difference however:

On the Vista machine:
Microsoft ADO Ext. 6.0 for DDL and Security

On the XP machine:
Microsoft ADO Ext. 2.8 for DDL and Security

I did some research and determined that this is part of MDAC and that in Vista the included version is 6.0 and there is no 6.0 version available to XP and 2.8 is the most recent (with Service Packs).

Additionally I read some information that indicated the erroring function "Left" is a part of VBE6.DLL and that's where I should look for the solution.

I saw one solution that recommended Late Binding to remedy this. I am not familiar with this but presented the option to the person creating the DB and apparently he isn't either.

Finally, I ran Windows Update on each machine in question and there were updates that hadn't automatically installed. These included .Net Framework 3.5 Update, Office 2007 Update, and Internet Explorer 8. After applying these on the machines in question I still have the error.
0
Comment
Question by:pred8tr
2 Comments
 

Accepted Solution

by:
pred8tr earned 0 total points
ID: 24426136
I asked the developer to remove all of the referenced libraries and add them back one by one in order to determine the unused and unneeded libraries. He came back to me shortly there after and indicated that by removing the Microsoft ADO Ext. 2.8 for DDL and Security library and recompiling it he was able to generate a runtime that worked on Vista and XP.
0
 
LVL 39

Expert Comment

by:thenelson
ID: 24428769
I have frequently found Access databases that were developed on pre Vista fail for various random reasons on Vista. Decompiling and recompiling on Vista usually resolves these problems. Try that first.

To decompile then recompile:
   in run: msaccess "dbPathName.mdb" /decompile
   Compact/repair:  in run: msaccess "dbPathName.mdb" /compact
   compile: in VB editor: debug> compile
   Compact/repair

   http://www.granite.ab.ca/access/decompile.htm
0

Featured Post

3 Use Cases for Connected Systems

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, testing some more, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

A simple tool to export all objects of two Access files as text and compare it with Meld, a free diff tool.
As tax season makes its return, so does the increase in cyber crime and tax refund phishing that comes with it
Familiarize people with the process of retrieving data from SQL Server using an Access pass-thru query. Microsoft Access is a very powerful client/server development tool. One of the ways that you can retrieve data from a SQL Server is by using a pa…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

778 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question