[AccessD] Error 51 in 2010

Hi Rocky --

If you're interested to try I can add (for starters) a new feature to
Access.PowerTools to list references of the currently opened mdb/mde marking
which ones are broken. I can release that "References Lister" plug-in
tomorrow with new Access.PoweTools setup just to demonstrate how it can be
done. You can use it there, and you can point to this tool to your customer
in Bahrain for them to check references of your app .mde on their system
(but they will have to have .NET Framework SP1 installed to run the tool. It
will be installed during add-in setup, it takes a few minutes but usually
runs without any issues.)...

...and when v.0.0.3 of Access.PowerTools will be released such a "References
Lister" plug-in will be possible to get developed by everybody: if I have
had v.0.0.3 currently released I could have made and released "References
Lister" plug-in in minutes - I can't do that now that quick as it still need
to deploy all the add-in executables, and I have to go to bed now as it's
12:00 AM (17FEB10) here...

Thank you.

--
Shamil

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
Sent: Tuesday, February 16, 2010 11: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
--

 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4872 (20100216) __________

The message was checked by ESET NOD32 Antivirus.

http://www.esetnod32.ru