Visual Basic and MS03-026 blaster patch

[Jeanne Neath]

A Visual Basic v.6 sp5 compiled program was working fine
(for several years) on several computers using Windows
2000 Professional before applying the MS03-026 patch for
the blaster worm. Now parts of the program do not work
correctly on multiple computers. The problem seems related
to forms using the ADO data control. The forms will no
longer bring up the data stored in an Access 97 database.
The forms where I didn't use the ADO data control to
connect to the database seem to be working fine. Is anyone
else having problems of this type?

 

[Greg Newkirk]

Absolutely.

I have an Access 2000 database that uses ADO to read
Oracle tables. When compiling the ADO code, I get the
following error:
'The instruction at "0x6507cb86" referenced memory
at "0xffffffff". The memory could not be "read".', then
Access of course shuts down.

Coming back in and avoiding executing or compiling the
code that references ADO, it compiles and runs fine. This
was all working fine a week ago, before I downloaded the
most recent Windows 2000 Professional updates.

The problem can be replicated on co-workers machines who
have also updated Windows 2000 Professional. I did find
one co-worker who has not applied any Windows updates (he
is running NT), and the database compiles and executes the
ADO code just fine. Just like mine did a week ago.
Backing out the last weeks updates is not an option,
primarily because the database is being developed for a
customer who is also applying the Windows updates.

Any suggestions, patches, or work-arounds would be
appreciated.

Or is this problem so new that no one else has hit this
problem yet?

To replicate the problem, apply all most recent Win 2000
updates. Then compile Access 2000 code that references
ADO.

Thanks for any help.