Here's a situation we have at our office here.

We have an access application that we run in three
different accesses (97, 2000, XP)

It will convert and compile fine between the three.

97 uses DAO 3.5, 2000 uses DAO 3.6 and XP uses DAO 3.61,
and all that is given.

The problem is here:

We work on the application on one computer in our office,
and compile it and it runs fine.

Then we give it to someone else to use (running the same
version of Access), it breaks.

It breaks in the queries, when a basic Function is used as
an expression like the "Format" Function or "Iif"
function.  I'm not sure of ALL the functions that break,
but these are the ones I was able to find.

Worth Noting: Custom Functions work fine, and Casting
(CDate, CInt, etc) work as well.

Our Solution, is to Go to References, and UnCheck the DAO
Version (3.5, 3.6, or 3.61 depending on the Access
version).  Save and Recheck the DAO Version. Then
everything works peachy.

Does anyone have an idea of what's going on?

Hey Jesse:
1. Do all the Access versions have all the service packs
installed, including JetSp6?  Check this out.
2. I heard through the grapevine that running a packaged
app that was not compiled on a 'clean' machine (by MS
standards, this means a machine on which 'nothing else'
than Access or Office XP Developer is installed), would
lead to crashing (your app is not packaged, but it is
compiled, so there may be a correlation here).  Although
this info was given to me by MS people, and I discovered
it was kind of a 'BS' argument on their side, it may be
worth a try.  You never know.
3. Of course, I think that Access VBA will yell at you if
you try to check ALL the DAO libraries's version in the
references, but did you try this, and compiling like that
to start with?  
4. The other thing is that you may want to compile on the
development machine using the one and only DAO library
reference that its target deployment machine will have,
and see if this works.  That would suck and force you to
yield 3 different .mdb's for deployment.  Maybe this
would actually work.
5. Try to start your app using a shortcut and
the /decompile option ("c:\...\xxx.mdb" /decompile).  
Then re-compile, then re-try to run your app on the other
machines.  TRY THAT AT FIRST. See Tony Toew's 'FYI
Decompile' posted eralier today.
Hope it helps.  In any case, you are not alone, believe
me...
Cheers: Phil;-)