dbTalk Databases Forums  

Protecting / complie MS Access

comp.database.ms-access comp.database.ms-access


Discuss Protecting / complie MS Access in the comp.database.ms-access forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Dr. Edmund M. Hayes
 
Posts: n/a

Default Protecting / complie MS Access - 09-26-2006 , 08:32 AM






I wrote a access program that works well enough that a handful of
people would like to buy it from me.
My problem is that if I sell it to someone there is no mechanism that
I know of to protect them from giving it to anyone they feel like.

The program produces reports that are specific to a particular
organization but that does stop anyone from just modifying that report
to make it specific to another organization, who they might have given
it to.

Is there a way to convert the ms access file so that none of the
database structure or reports can be modified?

Complying it to an exe file would work but I have no idea how to do
that.

Lastly I am not talking big sales numbers here so I do not want to
spend $1000 bucks to protect something I might only make $800 bucks
on.

Thanks

Reply With Quote
  #2  
Old   
Ira Solomon
 
Posts: n/a

Default Re: Protecting / complie MS Access - 09-29-2006 , 05:17 PM






The mechanism that you require is builtin.
Under Tools/DatabaseTools
you wiill find: Make MDE file/

The MDE file will have all the contents, forms, and code, but it can't
be played with. The user will be able to run reports and update data
(provided you provide forms to do so) Only compiled code is in there
so no one can copy your code.

There are some oddities in creating the MDE, what they are depends on
the version of Access and other issues.

If it refuses to create the MDE and you don't understand the error,
email me and I'll look at.

Good luck
Ira Solomon

On Tue, 26 Sep 2006 09:32:05 -0400, Dr. Edmund M. Hayes
<ed (AT) edhayes (DOT) com> wrote:

Quote:
I wrote a access program that works well enough that a handful of
people would like to buy it from me.
My problem is that if I sell it to someone there is no mechanism that
I know of to protect them from giving it to anyone they feel like.

The program produces reports that are specific to a particular
organization but that does stop anyone from just modifying that report
to make it specific to another organization, who they might have given
it to.

Is there a way to convert the ms access file so that none of the
database structure or reports can be modified?

Complying it to an exe file would work but I have no idea how to do
that.

Lastly I am not talking big sales numbers here so I do not want to
spend $1000 bucks to protect something I might only make $800 bucks
on.

Thanks

Reply With Quote
  #3  
Old   
Vince
 
Posts: n/a

Default Re: Protecting / complie MS Access - 01-13-2007 , 10:12 AM



here is a helpful guide for deploying a database:

http://msdn2.microsoft.com/en-us/lib...ffice.11).aspx


"Dr. Edmund M. Hayes" <ed (AT) edhayes (DOT) com> wrote

Quote:
I wrote a access program that works well enough that a handful of
people would like to buy it from me.
My problem is that if I sell it to someone there is no mechanism that
I know of to protect them from giving it to anyone they feel like.

The program produces reports that are specific to a particular
organization but that does stop anyone from just modifying that report
to make it specific to another organization, who they might have given
it to.

Is there a way to convert the ms access file so that none of the
database structure or reports can be modified?

Complying it to an exe file would work but I have no idea how to do
that.

Lastly I am not talking big sales numbers here so I do not want to
spend $1000 bucks to protect something I might only make $800 bucks
on.

Thanks



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.