Copyright

[mary.h]

Hi,
I've got written some code in Access, which now seems to interest people from other companies, but I'd like to sell it and don't know how I can prevent them from just copying my database.

Any suggestions out there.

Mary H.

 

[ghudson]

You can either convert it to a MDE or secure it using Access security [workgroups and permissions] and/or distribute a runtime version of Access or do all three. Nothing is hack proof these days but each one of those options will help protect your hard work. You will have to purchase the Office Developers Edition for the version of Office you are using and that will allow you to create a package and deploy with a setup.exe installation to disribute a royalty free runtime version of Access for which they can use your db.

I suggest that you search this forum for the keywords listed above for more info.

Please ensure that you make backup copies for you can not convert a MDE back to a MDB and you can lock yourself out of your db if you incorrectly apply security.

Good luck!

 

[The_Doc_Man]

If you specifically mean "Copyright" in the USA then there are some guidelines that you could explore by looking up the Copyright Act of 1975, which explicitly lays out the process for copyrighting software.

In brief, if you want to copyright something, you must send a copy of it to the U.S. Copyright office. If it is long enough, you can send excerpts of a sufficient size to properly represent the code and/or look-feel issues. If you don't want to actually copyright it but want to protect it anyway, you can go through the motions. However, if you DON'T actually copyright it, you cannot effectively sue for breach of copyright unless you complete the registration (unless the law has been amended AGAIN, and I wouldn't put it past congress.)

The object (as a whole) must include a declaration that comes up stating that it is a copyrighted work in its entirety, protected by U.S. Copyright laws. I suggest a startup form with a wordy message box might be good for this. It can be an OK-only message box.

You should also make EVERY FORM include the copyright symbol (c inside a circle or if you don't have one of those, c inside parentheses, plus the written-out word copyright and the date on which the copyright began, plus the name of the owner - you or your employer or whatever.)

EVERY MODULE should include a comment line with the same exact declaration. EVERY REPORT should include this as a part of the report header or report footer. Some folks make it Page Header/Footer instead if they are paranoid enough.

There are also international standards for copyrighting text material including programs, but you would have to look them up. I believe the specific language used in the copyright notice you display has to change vs. the USA version, but it is just text to be displayed. Essentially a constant.

 

[Pat Hartman]

ghudson, you mean .mde rather than .mdw. Also, the runtime edition does not in any way shape or form chang your db. All it does is provide a license to distribute the Access runtime allong with your application. While it is true that the runtime version of Access does not have the capability of opening a db in design view, if a user had a retail version of Access installed, he could simply use that to open your app. So, no, this does not provide any security at all.


mary.h, your best bet is a combination of things -
1. Access/Jet security
2. Distribute only the .mde
3. Add the proper copyright notices and register the copyright
4. Create your own registration procedure so that the customer needs to obtain a "key" everytime they "install" the app similar to what Microsoft does for Office.
5. Purchase a third-party product that provides a security "key".

 

[mary.h]

software registration procedure

Thank you all for your comments.

At the end I think it will be what Pat Hartman stated. Because all the above mentioned will not secure the db from being copied (file copy!), even so I understand that copyrighting would make it illegal (but who cares!). The db as such is already protected by access security (mdw) and the code is passwort protected too.

Pat have you any hints,where I can start with to make my own registration procedure? Are there any tools out there to help me? Do I need to purchase anything for it to work? (I am not yet considering a dongle solution, if there are other ways)

Mary H.

 

[Pat Hartman]

There have been solutions outlined here. Try searching for them.

 

[mary.h]

Hi Pat,

I've found these two posts interesting and one of them will be my solution I guess.

Access security via workgroup
http://www.access-programmers.co.uk/forums/showthread.php?t=4001

Registration process
http://www.access-programmers.co.uk/forums/showthread.php?t=61171

Thank you for this.

Mary.H

 

[pat_nospam]

Actually, I was looking at this recently. The Copyright laws have changed slightly and after talking with the office, they pointed me to their website. More or less, unless you are involved in litigation or dispute, your works are copyrighted as soon as you have them in a tangible form (i.e. on paper/code, not just in your head:

http://www.copyright.gov/help/faq/faq-general.html

Just thought this might help some people copyrighting their work.

When is my work protected?
Your work is under copyright protection the moment it is created and fixed in a tangible form that it is perceptible either directly or with the aid of a machine or device.

Do I have to register with your office to be protected?
No. In general, registration is voluntary. Copyright exists from the moment the work is created. You will have to register, however, if you wish to bring a lawsuit for infringement of a U.S. work. See Circular 1, Copyright Basics, section “Copyright Registration.”

If you specifically mean "Copyright" in the USA then there are some guidelines that you could explore by looking up the Copyright Act of 1975, which explicitly lays out the process for copyrighting software.

In brief, if you want to copyright something, you must send a copy of it to the U.S. Copyright office. If it is long enough, you can send excerpts of a sufficient size to properly represent the code and/or look-feel issues. If you don't want to actually copyright it but want to protect it anyway, you can go through the motions. However, if you DON'T actually copyright it, you cannot effectively sue for breach of copyright unless you complete the registration (unless the law has been amended AGAIN, and I wouldn't put it past congress.)

The object (as a whole) must include a declaration that comes up stating that it is a copyrighted work in its entirety, protected by U.S. Copyright laws. I suggest a startup form with a wordy message box might be good for this. It can be an OK-only message box.

You should also make EVERY FORM include the copyright symbol (c inside a circle or if you don't have one of those, c inside parentheses, plus the written-out word copyright and the date on which the copyright began, plus the name of the owner - you or your employer or whatever.)

EVERY MODULE should include a comment line with the same exact declaration. EVERY REPORT should include this as a part of the report header or report footer. Some folks make it Page Header/Footer instead if they are paranoid enough.

There are also international standards for copyrighting text material including programs, but you would have to look them up. I believe the specific language used in the copyright notice you display has to change vs. the USA version, but it is just text to be displayed. Essentially a constant.

 

[Cosmos75]

Just FYI, from http://VBAExpress
Thread: Copyrighting VBA Code?.

Also posted a link to this thread at the link above.