Thanks to all for your replies. < tic >

Actually, I found that DAO360 came in with SP3. So,
I don't know why SP4 screwed up VB6.

Evidently, there is some whacky application on my PC
that needs DAO350.dll and SP4 decided to take away
references to it by forcing DAO360.dll only in there.

What does VB look at it upon initialization that has the
references to DAO DLLs in it?

Regardless, I just did a REGSVR32 on the still existing
DAO350.dll and VB6 now runs again as it used to.