[AccessD] Hiding Table in mde

MartyConnelly martyconnelly at shaw.ca
Fri Feb 20 16:13:47 CST 2004


You can sort of hide the table if you preface table name with USys. It 
can then only be seen if you turn on System Objects view in options

Joseph O'Connell wrote:

>Rocky,
>
>Search the archives for "Copy Protection".  There was a long discussion of
>this topic and recommendations for several add-in products during October
>2001.
>
>Joe O'Connell
>
>
>-----Original Message-----
>From: Rocky Smolin - Beach Access Software <bchacc at san.rr.com>
>To: Access Developers discussion and problem solving
><accessd at databaseadvisors.com>
>Date: Wednesday, February 18, 2004 12:45 PM
>Subject: Re: [AccessD] Hiding Table in mde
>
>
>|A.D.:
>|
>|What I'm trying to do is copy protect my program by putting a data bomb in
>|the opening form.  Right now it's hard coded into the module's OnOpen
>event.
>|I was going to put the date bomb into a table but that table is accessible
>|to the user even in an mde.
>|
>|So I was trying to hide the table.  But a more direct way would be to be
>|able to alter the line of code in the mde which contains the expire date.
>|
>|I've cooked up a more elaborate scheme now but haven't settled on a final
>|approach.  I want the user to be able to call or email their serial number
>|and I give them a code to change the expiration date in their system.  I've
>|done a key like this before for another client so I've got all the
>|code/decode stuff worked out.
>|
>|I'm just searching around for the simplest solution to protecting my
>|product.
>|
>|Regards,
>|
>|Rocky
>|
>|----- Original Message -----
>|From: "A.D.Tejpal" <adtp at touchtelindia.net>
>|To: "Access Developers discussion and problem solving"
>|<accessd at databaseadvisors.com>
>|Sent: Wednesday, February 18, 2004 8:57 AM
>|Subject: Re: [AccessD] Hiding Table in mde
>|
>|
>|Rocky,
>|
>|    Could you kindly confirm that you wish to add a new program module for
>|manipulating existing objects in an mde - without having to go through the
>|conventional steps of first altering the code in original mdb and then
>|converting it into a fresh mde.
>|
>|    If this be the case, an interesting solution could be adopted, so as to
>|meet your requirement.
>|
>|Regards,
>|A.D.Tejpal
>|--------------
>|  ----- Original Message -----
>|  From: Charlotte Foust
>|  To: Access Developers discussion and problem solving
>|  Sent: Tuesday, February 17, 2004 23:10
>|  Subject: RE: [AccessD] Hiding Table in mde
>|
>|
>|  Code can't be modified in an mde at all, programmatically or otherwise.
>|  That's the whole point.
>|
>|  Charlotte Foust
>|
>|  -----Original Message-----
>|  From: Rocky Smolin - Beach Access Software [mailto:bchacc at san.rr.com]
>|  Sent: Sunday, February 15, 2004 9:55 PM
>|  To: Access Developers discussion and problem solving
>|  Subject: Re: [AccessD] Hiding Table in mde
>|
>|
>|  Doug:
>|
>|  That would work but I'd prefer not to have the file external.  Can code
>|  be modified programmatically in an mde?
>|
>|  Rocky
>|
>|  ----- Original Message -----
>|  From: "Doug Murphy" <dw-murphy at cox.net>
>|  To: "'Access Developers discussion and problem solving'"
>|  <accessd at databaseadvisors.com>
>|  Sent: Sunday, February 15, 2004 12:38 PM
>|  Subject: RE: [AccessD] Hiding Table in mde
>|
>|
>|  > One way to do this is to not put it in the database, but use an
>|  > external file that is encrypted.  Set the system up so it won't run if
>|
>|  > the file isn't present and make the file hard for folks to find.
>|  >
>|  > Doug
>|  >
>|  > Douglas Murphy
>|  > Murphy's Creativity
>|  > (619) 334-5121
>|  > doug at murphyscreativity.com
>|  > www.murphyscreativity.com
>|  >
>|  >
>|  >
>|  >
>|  > -----Original Message-----
>|  > From: accessd-bounces at databaseadvisors.com
>|  > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky
>|  > Smolin
>|  > - Beach Access Software
>|  > Sent: Sunday, February 15, 2004 7:41 AM
>|  > To: AccessD at databaseadvisors.com
>|  > Subject: [AccessD] Hiding Table in mde
>|  >
>|  >
>|  > Dear List:
>|  >
>|  > Is there a way to prevent a user from importing a table from an mde
>|  > into an mdb without putting a password on the mde?  I'm trying to
>|  > build a serial number/upgrade/license extension function into an app
>|  > and will be storing the data in a front end table.
>|  >
>|  > TIA,
>|  >
>|  > Rocky Smolin
>|  > Beach Access Software
>|_______________________________________________
>|AccessD mailing list
>|AccessD at databaseadvisors.com
>|http://databaseadvisors.com/mailman/listinfo/accessd
>|Website: http://www.databaseadvisors.com
>|
>|_______________________________________________
>|AccessD mailing list
>|AccessD at databaseadvisors.com
>|http://databaseadvisors.com/mailman/listinfo/accessd
>|Website: http://www.databaseadvisors.com
>
>
>_______________________________________________
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com
>
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada






More information about the AccessD mailing list