[AccessD] How to set up a license key for an AccessFE/BE system?

Hi Rocky

Or for this simple task, at zero cost, FreeBASIC:

  http://www.freebasic.net/index.php/about 

/gustav


>>> stuart at lexacorp.com.pg 08-03-2010 00:24 >>>
It comes from http://www.powerbasic.com 
It is commercial software.   However they have a great deal on at the moment on the 
previous version..

The current version 9 sells for $199.

Version 8 is  available as "Classic Powerbasic".  It normally sells for $99 but is currently on 
special for $49.

It probably could be done in VS - but not nearly as easily.

  
-- 
Stuart



On 7 Mar 2010 at 16:34, Dan Waters wrote:

> Where does PowerBasic come from?  Free download?
> 
> Could the same be done in VS?
> 
> Dan
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com 
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
> Sent: Sunday, March 07, 2010 4:24 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] How to set up a license key for an AccessFE/BE
> system?
> 
> If you are going to the extent of a separate file, I'd just create a  DLL in PowerBasic 
> containing the crypto functions and call it when required.  Much more secure, smaller, faster 
> and doesn't need referencing.  :-)
> 
> -- 
> Stuart
> 
> On 7 Mar 2010 at 21:50, Max Wanadoo wrote:
> 
> > What I would do is create the encrypt/decrypt code in a separate mdb, make
> > it an mde and encrypt that itself.
> > Rename it to something like, Mylibrary.lib
> > 
> > The in the main mdb, go to references and set a reference to it. The code
> > gets called to do its work but the user never gets to see the "inner workings".
> > 
> > Max
> > 
> > 
> > -----Original Message-----
> > From: accessd-bounces at databaseadvisors.com 
> > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart
> McLachlan
> > Sent: Sunday, March 07, 2010 9:19 PM
> > To: Access Developers discussion and problem solving
> > Subject: Re: [AccessD] How to set up a license key for an AccessFE/BE
> > system?
> > 
> > But you can't "hide" the decryption/validation code in an MDB.  There's no
> > need to hide dates/licence details at all if they are encypted.  It's the
> > code that has to be hidden.
> > 
> > --
> > Stuart