Forums Retired Products and Controls
Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
Close
Heinrich
20
Problems with Dateedit Control and Time Control
posted
Hello, we are developing with VB6 and we are using some components of the Ultra Suite 3.0.2 (dateedit Control and time control). These components are installed to our applikation path and also registrated there. Some customers use an other software which uses the same components. These software installs their components in the system32 directory. Now our software reply an error message whenever a formular will load where one of this components is used. The error code is 429. The only way to solve this error is to delete the 'new' components from the system32 directory and use the regsvr32 to register our components again. But on this way the other software will not work. Is there a posibility to use the components in our applikation folder and also let the other software use the components from system32 ? Or is there a other posibility to avoid this problem? This problem is really urgent because every day more customers announce this error message. best regards from germany Sebastian Neubner / Time iX
Parents
No Data
Reply
  • 139
    posted

    Hi I am still supporting an application with the same technology base that we are upgrading now. However we have come across these issues in the past and depends on what operating system you are using, and environment, so here is a quick list of things to check that can cause issues.

    • Windows 2000 - Must install via control panel
    • Win XP: Make sure firewalls and anti virus do not interfere. Make sure you have admin rights
    • Vista: (Yes they work on Vista nicely) Again make sure you install as "Administrator". make sure anti virus or firewalls do not block install. I have found even some anti spyware tools can sometimes stop access to registry etc during install process.
    • Look at what tools you are using to do your install on the client machines, and make sure they are registering the controls correctly. I still use wise 9 for these legacy applications, and it works nicely on XP and Vista.

     I know these are general, but should point into correct direction.

Children
No Data