This article has been archived. It is offered "as is" and will no longer be updated.
Question: When trying to connect to an ODBC DataSource using RDO within VBA, an error message is returned. It worked fine on the development machine but when transferring the project to another machine the following error: Run-time error '429' ActiveX component can't create object is returned. Why doesn't it work on the 2nd machine?
Answer: This actually is a built in limitation of VBA. While VBA allows you to create references to RDO on a development machine that has VB or C++ installed, it actually doesn't allow it to distribute this solution to a customer that does not have these tools installed. If VB or Visual C++ is installed (as in the situation above), it may work on the end user's machine but this solution isn't supported by Microsoft. The link below connects to a Microsoft Technical document that discusses this problem.
Microsoft Dynamics GP 9.0, Microsoft Business Solutions–Great Plains 8.0, Microsoft Great Plains eEnterprise 7.0, Microsoft Great Plains Dynamics 7.0, Great Plains eEnterprise 6.0, Great Plains Dynamics 6.0, Modifier with Visual Basic for Applications