Securing files so they can't be passed from one user to another

[Dave14867]

Hello All,



I am sure there are plenty here that create databases for sale/use by many users. How do you make it so one user cannot just pass a file to another and use it without paying for it?

[June7]

Probably the most can do is do all coding in VBA and publish as an executable. An executable is compiled so VBA code is not available to copy.

[Dave14867]

June7,

But then can't one person just pass the executable along to another?

Dave

[June7]

Yes, same as someone can pass MS Office to me. As long as I have the license certificate I can install it on any computer. Seems used to be able to build a license certificate for an Access db but I've never gone there and don't know what's available now. See what Google gives.

[isladogs]

You can distribute yourapps using an installer package which requires a license key.
Its impossible to prevent anyone copying your ACCDB /ACCDE file from another computer.
However you can add code to your application so it requires activation before it can be used fully.
The activation code can be tied to both the license key and a workstation.
This means that once activated for a particular workstation, it wouldn't be available elsewhere

Of course this has the same issue as any other application requiring activation.
If the licensed owner changes their hard drive or workstation, they will need to reactivate

[Micron]

It's nearly impossible - ask Bill.
Identifying the workstation (such as hard drive serial number) is one way, but then what do you do where the user is using terminal services? They don't have a hard drive of their own; it's only on the server and is shared by everyone else anyway.
How do you know the request to allow re-activation is legit because the hd was actually changed? It could just be that it's an attempt to install on a different machine. You need more than that to get closer to 100% lock down, which you never will achieve; at least not without raising the ire of IT people. You can only raise the level of protection from zero to something a bit higher. At least that's my take.

[isladogs]

My activation procedure is based on values from users hard drive, motherboard, CPU etc.
These create a unique set of values from which an activation ID is generated and emailed back to the client.
I am also able to check installations against license keys.
To the best of my knowledge my apps based on this system have not been installed 'illegally' or if they have, no attempt has been made to reactivate them

So far I've never been asked to reactivate for a different PC but if I was my inclination would be to authorise that.
Otherwise you would alienate your customers.
Microsoft have exactly the same policy. Reactivation via automated telephone system.
It takes several minutes to do but in my experience but they accept your answers and reauthorize the apps

Its MUCH easier to distribute apps with a site license allowing unlimited installations