Wrox Programmer Forums
Go Back   Wrox Programmer Forums > Microsoft Office > Access and Access VBA > Access
Access Discussion of Microsoft Access database design and programming. See also the forums for Access ASP and Access VBA.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Access section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old March 30th, 2006, 11:58 AM
Registered User
Join Date: Mar 2006
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default HELP - Access 2000 Runtime w Windows XP Compiled..

..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.
Old April 2nd, 2006, 01:48 PM
Friend of Wrox
Join Date: Mar 2004
Posts: 217
Thanks: 0
Thanked 1 Time in 1 Post

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?????


Old April 3rd, 2006, 11:06 AM
Friend of Wrox
Join Date: Dec 2005
Posts: 142
Thanks: 0
Thanked 0 Times in 0 Posts

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.

Similar Threads
Thread Thread Starter Forum Replies Last Post
SQL Server 2000 on Windows XP SP2 -- HELP ASAP reyboy SQL Server 2000 0 August 7th, 2005 02:10 AM
MS Analysis 2000 and WINDOWS XP Prof SP2 ZoroAstris SQL Server 2000 0 April 21st, 2005 04:44 AM
ADE file in Access 2000 <---> Access XP ginoitalo Access 3 April 14th, 2004 09:06 PM
Migrate Access XP to SQL Server 2000 Walden Access 1 September 21st, 2003 01:54 AM
Access XP VBA compatibility issues w/ Access 2000 bourgeois02 Access VBA 1 August 19th, 2003 04:14 PM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.