The corollary to this is that when you are installing the developer edition of crystal, it has to install the components for you to be able to build in it.
I agree with you on the missing .dll or .ocx, we just need to narrow down which it is (vb or crystal), so if after re-installing the vbruntime components it still gives that error, it is a .dll or .ocx on the crystal side, and we will go from there.
Main Topics
Browse All Topics





by: Shakti109Posted on 2004-01-16 at 10:10:32ID: 10131690
On the 'new' machines that are having the problem it is a good likelyhood that they are missing some of the VBRuntime components.
Rather than try to track down the exact component, re-install the VBruntime on one of your machines that get that 50003 error on, reboot, then try to re-run your app.
Let me know what happens after you re-install the VBruntime.