Rocky Smolin
rockysmolin at bchacc.com
Tue Feb 16 15:08:19 CST 2010
For over a year everything's been OK at this site. Suddenly this. Well, give me chance to shake out O2K10, I guess. But you're right - push comes to shove- they're going runtime. I have the script all ready to go because I do send the package occasionally to someone who doesn't have Access. r -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Murphy Sent: Tuesday, February 16, 2010 12:54 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Error 51 in 2010 Why don't you use a runtime? Everything stays independent of the Operating system and Office de jure. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin Sent: Tuesday, February 16, 2010 12:37 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Error 51 in 2010 The app is an mde - a package that I sell - and the user is not here - actually in Bahrain. But I'm going to put it on a test be I've got here - W7 r.c. (got noticed today by MS that it will be going away soon so I'd BETTER UPGRADE NOW!) AND Office 2010 pro r.c. We'll see. Since the version of this app has been in use in a lot of places including this user site, I think it must be something to do with O2K10. I don't have a reference checker. Do you know of one an one of those Access sites somewhere I could crib? TIA Rocky -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Kenneth Ismert Sent: Tuesday, February 16, 2010 9:22 AM To: accessd at databaseadvisors.com Subject: Re: [AccessD] Error 51 in 2010 > > Rocky Smolin: > I have an error report from an mde compiled in A2K3 but the client > appears to be running it with Access 2010. The error is 'Error 561 - > Internal Error'. Can't find out anything about this error. The > version of the mde they're running is a few minor releases back and is > solid. So I'm thinking this is a 2010 related problem. Any clues? > Check your VBA project references. This sounds exactly like the error I got when added a cdosys.dll reference to send email over SMTP. If you have a reference checker built-in to your code, run it and it may show the broken reference. Otherwise, plunk a development mdb on the machine, and see if any references are missing/broken. -Ken -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com