Yup, that could be the result of an update. I'm kind of wondering which
updates it gets, too; soulds like probably the UK versions.
You should be able to identify the updates that came in Thursday or
maybe Wednesday late, and uninstall them from Add/Remove. You might
have to tick the "show updates" box if it isnt' already ticked.
Then you can scroll down to Windows XP or whatever the entry is on
your machine, and see all the updates along with the date when they were
installed. Look for last Wed or Thurs dates. There you can uninstall
the updates one at a time until you've backed them all out.
I know it's a pain, but I would do a Restart after each removal, just
to help Windows keep track of things.
Another way to do that is to go to C:\windows\ and view the updates and
uninstall packages there. It's better to use Add Remove IMO, but ...
ymmv I suppose. The uninstallers also contain the KB article that
describes the updates if you want to chase down the particular one that
is causing the problem and uninstall just that one. KBxxxx-y can each
be looked up at the MS site to see what they were for.
Caveat: The author of your VB6 app may be aware of this problem and may
have a patch for the VB program ready instead of messing with the
updates.
Personally, that would be the first place I would check. If you're
right any and all with that prog on XP are going to have your problems
so there will be a want on his part to correct the issue. If it was a
prog crafted just for you, then he has even more impetus to correct it
for you, hopefully free of charge, assuming he's a good consultant.
HTH
Twayne
