The Eval function is supposed to evaluate Access/VBA expressions which
result in a string or numeric value.  This includes expressions which
contain built-in functions, such as "Int()" or "Rnd()".  But in Access 97,
it seems that passing the Eval function an expression which contains a
function call only works as long as the Eval function is being executed
from a module in the CURRENT database.  If it is placed in an Add-In ".mda"
database, and that database is started as an Add-In (from the
"Tools/Add-Ins" menu) then the Eval function fails with error code 7960:

"There was an error compiling this function.  The Visual Basic module
contains a syntax error.  Check the code, and then recompile it."

This used to work in Access 95.  Has MS ruined the Eval function in 97, or
am I doing something wrong?

Comments will be much appreciated.

Looks like it's even more broken than I thought. I've had similar problems
calling custom add-in functions using Eval, but I'm surprised that it even
breaks calling built-in functions!

I was told by MS that my problem was "as-designed", as it can be overcome
by making a reference to the add-in database from the current database. I
think this is an unacceptable requirement for users of the add-in.

I suggest you submit a bug report on www.microsoft.com.

Glen