Recent content by Alisa

Well I have XP and 2000 machines, do you think it would install on either of those?

Does anyone have a copy of VB3 they would be willing to give or sell me? Or know where I can find one?

Interesting question, I put in exactly as much effort as is necessary for the solution to be maintainable and decipherable, and not an ounce more. I specifically name any object that I work with in code, and leave everything else to whatever Access decided to name it. I do follow standard...

Wow. Who would have predicted that a thread complaining about ad placement would turn into the stock political argument of AWF? On second thought, probably anyone familiar with this forum would have predicted that. I still find the ads horrendously annoying, but it sounds like it is just me -...

Sounds like you've got it pretty well worked out - I hope your deployment goes well.

Also, what stops them from copying the mde to multiple computers after activation?

Yes, thats a creative solution, but not really what I'd call a commercial distribution . . . what if you wanted to sell 5000 copies, that would be a ridiculous amount of work!

So every customer gets a unique installer?

It looks like you have a good start, I hope it works well for you. I may not be understanding your code properly, but it looks like they could enter any value and as long as that value hadn't been entered before, it would be valid.

Having a custom built installer kind of means you aren't doing a commercial distribution, right? If you do a phone home scenario, if you don't encrypt the communication, there is nothing to stop someone from sniffing out the calls to your server. They could then use that information to write...

So what's to stop them from running the installer on another computer with the same activation key? How does the prepackaged program know that a particular activation key has already been used?

Well it is pretty easy to have a code that is too much trouble to hack. The issue is how does the Access application know that the activation has occured, and how do you keep people from fooling the application into thinking that the activation has occured? For instance, if you do the...

Right, well now we are back to what is appropriate for different scenarios. If you are attempting to sell a commercial product, then there is incentive to get it for free.

Obviously you won't want to discuss exactly how this works in a public forum, but I am curious about how you accomplish this. For instance, once your program is intalled on one computer, what stops someone from simply copying the mde, backend, etc. to another computer?

Bingo. You can spend all the time in the world trying to lock down an Access application, but at the end of the day, your time would be better spent upgrading to a solution that is appropriate for the scenario.