formerTexan
Programmer
This problem is occuring with A2K and A2003 running on NT2000.
When any form with a RichText ActiveX control (in this case, version 6.0) is opened (in any view) for the first time during a session, a cd burning software (OEM with the computer) repeatedly attempts to run an installation from the D drive.
Using Windows Task Manager to close the intrusive installation results in the Access application being closed as well. Windows Task Manager points to the process of the “Easy CD Creator 5.0 Basic” as being Access. Only by individually closing a lengthy series of installation popup windows can I then proceed with using the Access application. Then there will be no further problems for the remainder of the session.
So far I have tried removing the RTF reference from the reference library and on the chance I had an infected OCX file (RICHTX32.OCX), I replaced it. The problem remains.
I generally stay away from ActiveX controls, but it was useful in this situation. SO while removing the Richtext control seemingly alleviates the problem, it leaves something to be desired as a solution.
I'm over my head on this one. Any suggestions, guesses or answers.
Thanks,
Bill
When any form with a RichText ActiveX control (in this case, version 6.0) is opened (in any view) for the first time during a session, a cd burning software (OEM with the computer) repeatedly attempts to run an installation from the D drive.
Using Windows Task Manager to close the intrusive installation results in the Access application being closed as well. Windows Task Manager points to the process of the “Easy CD Creator 5.0 Basic” as being Access. Only by individually closing a lengthy series of installation popup windows can I then proceed with using the Access application. Then there will be no further problems for the remainder of the session.
So far I have tried removing the RTF reference from the reference library and on the chance I had an infected OCX file (RICHTX32.OCX), I replaced it. The problem remains.
I generally stay away from ActiveX controls, but it was useful in this situation. SO while removing the Richtext control seemingly alleviates the problem, it leaves something to be desired as a solution.
I'm over my head on this one. Any suggestions, guesses or answers.
Thanks,
Bill