Crescent ocx registration
Posted on 1998-06-24
This probably isn't that hard, but it's worth the rest of my points to me.
I d/loaded a crescent quick pack - demo version, you can play with them all you want, but can't create executables with them.
That's fine, but I then got a project to finish that uses some of them. They were already paid for by the folks that originally created the program. I'm just making a few changes. I get the feeling that everything would've been fine if I hadn't installed the Crescent demo in the first place, but now I can't get rid of it, and can't deploy the app.
I've removed all crescent references from my registry (with a backup), I've replaced all the .ocx's on the drive with the ones that came with the source code. The Crescent software was installed prior to this installation of VB5 (I was using 4 before), so it can't have infected VB, right?
When I try to make the executable (or make a setup), I get the same dialog that tells me I need to register, and the activeX components aren't compiled into the exe.
If I get more points, I'll raise the value - I'll try basically anything, tho I'd like to avoid reformatting. ;)