ART2000 Runtime Error - Function is not available in expressions in query expression

[Dr. Know]

Greetings,

Among the MANY other incompatibilities with ART2000, a new one has
cropped up. We have been careful to avoid the ART cannot use 'new
basic functions' problem. And now this...

I have a form with a drop-down combo box. Code inserts the row source
of the combo box to:

SELECT Format([SessionDate],"General Date") AS [Select Session] FROM
tblEMailLog Group By Format([SessionDate],"General Date") ORDER BY
First(tblEMailLog.SessionDate);

Works fine on Access 2000 SP3 and Access 2003 on all machines.
However, on the test machine with Access Runtime supposedly updated to
SP3, we get this error when clicking the combo box:

Function is not available in expressions in query expression
'Format([SessionDate],"General Date")'

Does anyone know what is going on... this time around?

Thanks,
Greg





Dr. Know

 

[david epsom dot com dot au]

Reference problem:

Function Isn't Available in Expressions in Query Expression
http://support.microsoft.com/default.aspx?scid=kb;en-us;194374

(david)

 

[Dr. Know]

david epsom dot com dot au said:

Reference problem:

Function Isn't Available in Expressions in Query Expression
http://support.microsoft.com/default.aspx?scid=kb;en-us;194374

(david)

Oops, I should have caught that. I remember reading this caveat a
while back - being old has it's disadvantages... ;-)

Or maybe it's just that there is such a LONG list of 'features' to
remember about Win2000/2003/98/Server/Access/Office/SQL etc...

Thanks for the pointer....
Greg





Dr. Know

 

[Dr. Know]

david epsom dot com dot au said:

Reference problem:

Function Isn't Available in Expressions in Query Expression
http://support.microsoft.com/default.aspx?scid=kb;en-us;194374

(david)

It turned out to be a reference to MDAC 2.6, which I found by
including parts of the code on the page you referenced.

Unfortunately, the correct references code doesn't work in an MDE,
'cause there is no module re-compile and save option in runtime.

But at least I can now present a message box explaining the lost
reference to the user... Beats the totally dysfunctional message we
got previously.

Don't even ask why we are using MDAC2.6. Ugghh...


Thanks again,
Greg






Dr. Know