[AccessD] Microsoft Update June 2026 - Strange Issues With VB6 Com+ Objects

[Jim Dettman]

Ditto what Gustav said.

Also, COM is on its way out, and I doubt Microsoft is paying much attention
to it, but with that said, they can't afford to be breaking things at this
point either.   COM should be usable for the next 4-5 years at least (2029
is when Outlook will lose COM support and it will be downhill from there).

Few more details would be helpful.  In the case of Access for example, I
would do a decompile of the apps.   I've noticed VBA getting more flakey
than it has in the past and doing weird things along the lines of what you
mention.   I think that's a byproduct of changes in Access.   Ever since
going to O365, things don't seem to get tested as much, and many features
are not fully baked in, but released over time.   In some ways, that's good,
and in others, not so good.

Jim.

-----Original Message-----
From: AccessD On Behalf Of Paul Hartland via AccessD
Sent: Wednesday, June 17, 2026 7:22 AM
To: Access List <accessd at databaseadvisors.com>
Cc: Paul Hartland <paul.hartland at googlemail.com>
Subject: [AccessD] Microsoft Update June 2026 - Strange Issues With VB6 Com+
Objects

To all,

Not sure anyone will get this, as I don't tend to see many postings from
AccessD anymore.  Since the latest Microsoft patches have been installed on
our servers at work, com+ objects that were built using VB6 that have
worked for years, suddenly giving unexpected results.  i.e. type mismatches
etc and blanking variables that have been passed to functions inside
classes, when there doesn't seem to be another assignment of that variable
anywhere.

Was just wondering if anyone had similar problems with any MS Access
systems etc

Thanks in advance for any help.

-- 
Paul Hartland
paul.hartland at googlemail.com
-- 
AccessD mailing list
AccessD at databaseadvisors.com
https://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com