..I have upgraded my development machine to Windows XP SP 2 from Windows 2000.

1) I am using Access 2000 to develop.

2) The end-user's machine uses Access 2000 Runtime to open the application. (Access is not installed on any of the end-user's machines.)

3) When I compile and build an .mde to be pushed to the end-user they get an error message that reads "Cannot find specified function". The application then shuts down.

Note: End-user OS's may vary from NT 4.0 to Windows XP SP 2, but there has never been a problem until I upgraded the development machine and compiled the same application.

Please advise.

Is it only one machine that is erroring?

Don't know if this is of any help or if it may apply. I recently created an MDB on my personal machines running XP-Home and XP-Pro. MDB would not install onto my work machine running Win2K, but did install after XP-Pro was installed. HOWEVER, the MDB kept failing at several VB and built-in functions (getobject with same error description you are getting, date() with #ERROR, forms that just corrupted after being opened in design view, and several other very annoying things just slowly started failing). After our Tech re-installed XP-Pro have had no further problems. Both machines have full A2k licenses. Have not installed our MDB on any of our machines with A2K Runtime and have not tried the file as an MDE. Just a thought, you don't have "add-ins" that Package and Deploy missed?????

HTH,
Loralee

I had a similar problem, the issue was that I had to explicitly declare my functions (specifically time() and date()). Easiest way to debug is to get an uncompiled version of the DB and find out where the line of code is that needs to be explicitly declared.