W
wizbang
Guest
Greetings,
I developed an Access 2000 Application that uses WinSock.
my machine
(XP Professional SP1, ACCESS 2003 created app in Access 2000 file mode, Visual Basic 6.0, .NET etc)
client machine
(XP SP2, ACCESS 2003)
When I copied the app to the client machine I ran into two missing references
Microsoft XML, v5.0 (MSXML5.DLL)
Microsoft Winsock Control 6.0 (SP5) (MSWINSCK.OCX)
I expected some problems, because I have had prior experience with the missing XML Reference.
Here is what I did to resolve that problem.
- Downloaded MSXML5.DLL and placed it in C:\WINDOWS\SYSTEM32
- Issued the following command in Run:
regsvr32 \windows\system32\MSXML5.DLL
- DllRegisterServer in \windows\system32\ MSXML5.DLL succeeded.
_____
- Downloaded MSWINSCK.OCX and placed it in C:\WINDOWS\SYSTEM32
- Issued the following command in Run:
regsvr32 \windows\system32\MSWINSCK.OCX
- DllRegisterServer in \windows\system32\MSWINSCK.OCX succeeded.
_____
- Did a System Restart.
- Opened the MS Access Application back
- In Microsoft Visual Basic I went to the References.
- The XML reference was there and I selected it.
(A small anomaly occurred in that I had to Browse for the Winsock reference from the system32 folder.)
- Browsed and selected the MSWINSCK.OCX and it brought the Microsoft Winsock Control (SP5) reference in.
- pressed OK and closed the References window.
- In VB, under Debug, I did a compile with no errors.
- Saved the work
When I opened the form and tested the application I received an error:
Run-time error 429
ActiveX component can't create object.
The offending code line being:
Set mnasock = New Winsock
(***here is the declaration statement at the top of the program listing)
(***here is the entire function with the offending line)
I researched the web and discover from microsoft's site symptoms and resolutions
I went down the list:
SYMPTOMS
Cause 1: DAO Is Not Properly Registered
regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\DAO360.DLL"
succeeded.
Cause 2: One or More References Are Missing
Those have been resolved
Cause 3: There Is a Utility Database Reference That Is Not Valid
N/A
Cause 4: You Do Not Have the Required Permissions for Required Libraries
Both my machine and clients machine user has administrator privileges.
Cause 5: There Is a Damaged Wizard File
Does not appear to be damaged (I have not used it)
I went and found a registry monitor and created another form in Access that had a single button that called the initializeWinSock function.
way down the list there was an entry that had the following:
139.44714355 MSACCESS.EXE:3124 QueryValue HKCR\TypeLib\{248DD890-BB45-11CF-9ABC-0080C7E7B78D}\1.0\0\win32\(Default) SUCCESS "C:\windows\system32\MSWINSCK.OCX"
Okay, that is about all I know how to do.
I am stumped.
anyone have any ideas? Something simple that I have overlooked?
Many thanks in advance,
wizzie
PS I don't have 24/7 internet access, it may be middle of next week before I can view, respond, or thank anyone.
I developed an Access 2000 Application that uses WinSock.
my machine
(XP Professional SP1, ACCESS 2003 created app in Access 2000 file mode, Visual Basic 6.0, .NET etc)
client machine
(XP SP2, ACCESS 2003)
When I copied the app to the client machine I ran into two missing references
Microsoft XML, v5.0 (MSXML5.DLL)
Microsoft Winsock Control 6.0 (SP5) (MSWINSCK.OCX)
I expected some problems, because I have had prior experience with the missing XML Reference.
Here is what I did to resolve that problem.
- Downloaded MSXML5.DLL and placed it in C:\WINDOWS\SYSTEM32
- Issued the following command in Run:
regsvr32 \windows\system32\MSXML5.DLL
- DllRegisterServer in \windows\system32\ MSXML5.DLL succeeded.
_____
- Downloaded MSWINSCK.OCX and placed it in C:\WINDOWS\SYSTEM32
- Issued the following command in Run:
regsvr32 \windows\system32\MSWINSCK.OCX
- DllRegisterServer in \windows\system32\MSWINSCK.OCX succeeded.
_____
- Did a System Restart.
- Opened the MS Access Application back
- In Microsoft Visual Basic I went to the References.
- The XML reference was there and I selected it.
(A small anomaly occurred in that I had to Browse for the Winsock reference from the system32 folder.)
- Browsed and selected the MSWINSCK.OCX and it brought the Microsoft Winsock Control (SP5) reference in.
- pressed OK and closed the References window.
- In VB, under Debug, I did a compile with no errors.
- Saved the work
When I opened the form and tested the application I received an error:
Run-time error 429
ActiveX component can't create object.
The offending code line being:
Set mnasock = New Winsock
(***here is the declaration statement at the top of the program listing)
Code:
Private WithEvents mnasock As Winsock
(***here is the entire function with the offending line)
Code:
Private Function initializeWinSock() As Boolean
On Error GoTo Err_initializeWinSock
initializeWinSock = True
Set mnasock = New Winsock
Exit_initializeWinSock:
Exit Function
Err_initializeWinSock:
initializeWinSock = False
MsgBox Err.Description
Resume Exit_initializeWinSock
End Function
I went down the list:
SYMPTOMS
Cause 1: DAO Is Not Properly Registered
regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\DAO360.DLL"
succeeded.
Cause 2: One or More References Are Missing
Those have been resolved
Cause 3: There Is a Utility Database Reference That Is Not Valid
N/A
Cause 4: You Do Not Have the Required Permissions for Required Libraries
Both my machine and clients machine user has administrator privileges.
Cause 5: There Is a Damaged Wizard File
Does not appear to be damaged (I have not used it)
I went and found a registry monitor and created another form in Access that had a single button that called the initializeWinSock function.
way down the list there was an entry that had the following:
139.44714355 MSACCESS.EXE:3124 QueryValue HKCR\TypeLib\{248DD890-BB45-11CF-9ABC-0080C7E7B78D}\1.0\0\win32\(Default) SUCCESS "C:\windows\system32\MSWINSCK.OCX"
Okay, that is about all I know how to do.
I am stumped.
anyone have any ideas? Something simple that I have overlooked?
Many thanks in advance,
wizzie
PS I don't have 24/7 internet access, it may be middle of next week before I can view, respond, or thank anyone.