[AccessD] Using ADO and Windows 7 SP1? Be careful!

Drew Wutka DWUTKA at Marlow.com
Thu Mar 31 09:46:30 CDT 2011


Speaking of the .Net world.... I ran into something the other day in VB.Net

In VB 6 (or VBA) if I had a custom class, let's say like this:

Public SomeStringProperty As String
Dim intSomeNumericValue as Long
Property Get SomeNumericValue() as Long
SomeNumericValue=intSomeNumericValue
End Property

I considered both 'SomeStringProperty' and 'SomeNumericValue' as properties of the class.  VB.Net does not. If it is defined with a Public variablename As SomeType VB.Net considers it a 'field'.

Interesting.  Not that it makes a whole hell of a difference now that I know, it drove me nuts while trying to put the 'properties' of a class into a combo box, and couldn't for the life of me figure why it kept returning an empty array! LOL

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
Sent: Wednesday, March 30, 2011 10:09 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Using ADO and Windows 7 SP1? Be careful!

Developers who actually used ADO (yes, there were a few of us) are
being pushed kicking and screaming into the .Net world.  Just because
backwards compatibility used to be a Microsoft byword, doesn't mean we
can depend on that any more.  With Windows 7, especially, you have to
watch out for older apps that won't run properly in that environment.

Charlotte Foust

On Wed, Mar 30, 2011 at 7:58 PM, Doug Steele <dbdoug at gmail.com> wrote:
> I had a call from a client this morning.  Some code that I had written
> using ADO to write records to a back end, code which has been working
> for 2 or 3 years, was crashing with a message indicating that ADO
> wasn't working.  Unfortunately, it was a bit of a panic situation and
> I didn't get a screen dump of the message.  I putzed around with the
> references and re-compiling, and got it to work.  Turns out that this
> is probably an example of a known problem:
>
> http://support.microsoft.com/kb/2517589
>
> There is also a discussion (well, a bunch of bitching) about this in
> the LinkedIn Access Developers group.  If I understand it correctly,
> an Access database using ADO which is compiled on a computer running
> Windows 7 SP1 will NOT run properly on any other version of Windows.
> I`m running Win7 SP1 and my client is Win7, so I guess this was the
> problem.
>
> I wonder if I can send an invoice for my debugging time to Microsoft...
>
> Doug
> --
> 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
The information contained in this transmission is intended only for the person or entity 
to which it is addressed and may contain II-VI Proprietary and/or II-VI Business 
Sensitive material. If you are not the intended recipient, please contact the sender 
immediately and destroy the material in its entirety, whether electronic or hard copy. 
You are notified that any review, retransmission, copying, disclosure, dissemination, 
or other use of, or taking of any action in reliance upon this information by persons 
or entities other than the intended recipient is prohibited.





More information about the AccessD mailing list