The business about set creating a pointer to an object and not a copy is spot on.
Why not create your local object and then pass over the properties from the global object.
Thanks AdaHacker but perhaps I didn't put the problem clealrly enough. My custom installation will use floppy and CD media. Part of the installation will modify the floppy content, I want to prevent someone copying the unmodified version.
I'm setting up a customised installation program by modifying the Setup1.exe.
Is there a way to prevent anyone from copying files from the installation media? This will be a CD and a floppy, and it's the floppy I'd like to crack first.
We have SQL7 running on a quad processor, 1 Gig RAM, NT4 machine, which has recently started leaking memory badly. For other reasons I've recently implemented MTS components on a different machine and enabled connection pooling which is working fine. We also run a number of Access based...
I came into this game(?) through a very similar route. With a lot of help from my family I ended up with a training passport from LearningTree in London, UK. And this was excellent, I cannot recommend them strongly enough. Otherwise SAMS TeachYourself in 21 days are good to get you off the...
I've periodically tried to create a multi-column dropdown combo in VB6 but without success. I'm trying to replace Access aps with VB equivs but this will be a stumbling point. Any ideas anyone?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.