topfuelbob- (name?)
It's not specifically the version that's getting you. When queries stop
recognizing simple builtin functions like IIf and Date, it usually means the
database has a VB reference to a library not on the machine. On your machine,
open the database in a retail copy, open the VB Editor, and choose References
from the Tools menu. Remove any libraries that you don't actually need. The
basic libraries required are:
Visual Basic for Applications
Microsoft Access 12.0 Object Library
Microsoft Office 12.0 Access database engine Object Library
Try removing all but these three libraries, then do a compile. If that works,
save the compile, compact and repair, and give your users the new database.
John Viescas, author
Microsoft Office Access 2010 Inside Out
Microsoft Office Access 2007 Inside Out
Building Microsoft Access Applications
Microsoft Office Access 2003 Inside Out
SQL Queries for Mere Mortals
http://www.viescas.com/
(Paris, France)
---------------------------------------
From: MS_Access_Professionals@yahoogroups.com
[mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of topfuelbob
Sent: Monday, March 19, 2012 12:25 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Problem with dates in queries
I have a calculated field in a query which works fine for all my users that have
runtime 12.0.6612.1000.
But for all my users that have runtime version 12.0.6425.1000 it fails with the
error:
"3075 (Function is not available in expressions in query expression)"
The field value in the query is:
"ActiveContract: IIf([ContractStartDate]<Date() And Not
[ContractEndDate]<Date(),True,False)"
So, question, am I using the correct syntax in that field?
We are all in the UK but as far as I can tell, all machines are set up with the
same regional settings regarding dates.
Tidak ada komentar:
Posting Komentar