Office 2016 Access VBA sending XML (1 Viewer)

ActiveX component can't create object"

This error message does not necessarily mean that an ActiveX control is involved. For example, one possible cause is that DAO, which is an ActiveX component, cannot create an object because the DAO Automation Server cannot start. Frequently, the cause is that DLLs that provide referenced functionality for the program are not registered or are incorrectly registered.

Click to expand...

jessss said:

Found reason why its stopped working, it was because I was using 64 bit office 2016 instead of 32 bit. Problem is now solved. But thanks for replying

Click to expand...

Microsoft SOAP Toolkit provides limited support for applications that must run on the Microsoft Windows Server 2003 operating system. Please note that all SOAP Toolkits have been replaced by the Microsoft .NET Framework. SOAP Toolkit versions earlier than version 3.0 are no longer supported. Standard support for SOAP Toolkit 3.0 expired March 31, 2005, and extended support will expire March 31, 2008.

SOAP Toolkit Version 2.0
SOAP Toolkit version 2.0, including Service Pack 1 (SP1) and Service Pack 2 (SP2), is no longer supported.

If your application uses SOAP Toolkit version 2.0 to develop XML Web services and you plan to host these services on the Windows Server 2003 operating system, Microsoft recommends that you do one of the following:
Use the Microsoft .NET Framework (that is, implement .NET XML Web services or use .NET Remoting).
Use COM+ SOAP feature on Windows Server 2003.
If your application uses SOAP Toolkit version 2.0 to consume XML Web services and must run on the Windows Server 2003 operating system, Microsoft recommends that you use Microsoft .NET Framework to consume the XML Web Service.
SOAP Toolkit Version 3.0
Microsoft does not recommend that you use SOAP Toolkit 3.0 on computers that are running Windows Server 2003. There is limited support for Soap Toolkit 3.0 when you upgrade existing applications from earlier versions of Windows to Windows Server 2003. No new development should be performed with SOAP Toolkit 3.0. Existing applications that are built on SOAP Toolkit should be upgraded to a .NET-based solution as soon as possible.

SOAP Toolkit version 3.0 client components and corresponding low-level client-side APIs are supported on the Windows Server 2003 operating system in limited scenarios. The client components and low-level client-side APIs are supported in desktop client application scenarios. They are not supported in server-side (middle-tier) application scenarios.

SOAP Toolkit 3.0 server components and SOAP Toolkit ISAPI Listener are not supported on the Windows Server 2003 operating system.

If your application uses SOAP Toolkit version 3.0 to develop XML Web services, Microsoft recommends that you do one of the following:
Use the Microsoft .NET Framework (that is, implement .NET XML Web Services or use .NET Remoting).
Use COM+ SOAP feature on Windows Server 2003.
References

For more information, visit the following Microsoft Developer Network (MSDN) Web sites:
Creating XML Web Services in Managed Code
http://msdn2.microsoft.com/en-us/library/3x5e7527(vs.71).aspx

An Introduction to Microsoft .NET Remoting Framework
http://msdn2.microsoft.com/en-us/library/ms973864.aspx

COM+ Web Services: The Check-Box Route to XML Web Services
http://msdn2.microsoft.com/en-us/library/ms973810.aspx

Click to expand...