T
tudor
I have an Access 2003 ADP application that had/has a form with a Winsock
control in it. All worked brilliantly until about 10 days ago (XP, Vista,
2003 machines in multiple locations): "There is no object in this control".
We haven't made ANY changes to the application in over a year, so I strongly
suspect that Windows Update is the culprit.
I tried to readd the Winsock control to the form using Insert>ActiveX
Control>Microsoft WinSock Control, version 6.0 and received "[Application
Name] doesn't support this ActiveX Control". I tried to unregister and
reregister c:\windows\system32\mswinck.ocx and then tried to readd the
control - that didn't work.
The control on the form is OLE Class: Winsock, Class: MSWinsock.Winsock.1 -
and it looks fine.
And just to make sure the ADP wasn't the issue, I created a blank .mdb
database, created a new form, inserted the Winsock control and got:
"Microsoft Office Access doesn't support this ActiveX control."
Has anyone else run into this issue? This is a major drag... our application
is totally cut off from a bunch of other systems without winsock support.
control in it. All worked brilliantly until about 10 days ago (XP, Vista,
2003 machines in multiple locations): "There is no object in this control".
We haven't made ANY changes to the application in over a year, so I strongly
suspect that Windows Update is the culprit.
I tried to readd the Winsock control to the form using Insert>ActiveX
Control>Microsoft WinSock Control, version 6.0 and received "[Application
Name] doesn't support this ActiveX Control". I tried to unregister and
reregister c:\windows\system32\mswinck.ocx and then tried to readd the
control - that didn't work.
The control on the form is OLE Class: Winsock, Class: MSWinsock.Winsock.1 -
and it looks fine.
And just to make sure the ADP wasn't the issue, I created a blank .mdb
database, created a new form, inserted the Winsock control and got:
"Microsoft Office Access doesn't support this ActiveX control."
Has anyone else run into this issue? This is a major drag... our application
is totally cut off from a bunch of other systems without winsock support.