Unregistered
November 3, 2002, 00:41:32
Found the solution to my prior post and it may help some of your readers.
We switched to ADO and we used the ADO data object OCX. Turns out that you must deploy AND register MSBIND.DLL with the MSADODC.OCX data bindong control. The MSBIND.DLL is the gatekeeper for the OCX. Deploying both and registering the DLL gets this to work fine. We converted our project and everything went fine. We even got rid of all ADO connections. But the ADO data control was still used for the TX control and well, we got no connection and no error message. This solves the problem.
Joe.
This message was originally posted by Joe Caplan in the old TX Text Control Support Forum.
We switched to ADO and we used the ADO data object OCX. Turns out that you must deploy AND register MSBIND.DLL with the MSADODC.OCX data bindong control. The MSBIND.DLL is the gatekeeper for the OCX. Deploying both and registering the DLL gets this to work fine. We converted our project and everything went fine. We even got rid of all ADO connections. But the ADO data control was still used for the TX control and well, we got no connection and no error message. This solves the problem.
Joe.
This message was originally posted by Joe Caplan in the old TX Text Control Support Forum.