using mde files in different operating systems

[ruth]

I'm developing an Access database under Win2000. My clients have a variety of
operating systems. I don't want to have to know what they are using and every
time they upgrade. I can't have every combination on my own computers to
develop with either. I am using late binding everywhere I can in code. And I
also tried to follow the suggestions in
www.trigeminal.com/usenet/usenet026.asp in so far as I could understand them
applying to my problem. So I have an autoexec function that does all its own
disambiguation, but that doesn't help me with queries.

My queries use built-in functions. These are giving "Function isn't
available in query expression" and other errors when called in XP or Win98.
How can I use late binding for VBA? I know I can't fix up references like I
can with mdb files, but is there any way I can develop one database that will
work on different computers? Is there something I can do in my autoexec
function that will insure that Access can run its VBA functions in queries?

 

[Lance McGonigal]

Sounds like the main problem you're having is broken references. Figure out
what reference you need to run and then break and rebuild the reference with
every start. This is a good way to make sure it ALWAYS runs.

HTH.