[AccessD] Hiding Back End Design

Hi Rocky

No, you cannot open or attach tables from the BE without the correct
password. But as stated from several already, you can google up at
least three password crackers.

Next step would be Access security as mentioned by Drew, and the next
would be to apply field encryption which is a major step.

By why not turn it completely around: make the design open and
documented as "this is the way to build a database for an application
like this"? Then you are the master and everyone else is the
replicant - following the "Rocky" standard. Personally, I think the
time for proprietary systems has passed - customers need systems they
can drag data from to be used elsewhere.

Also, I really doubt someone can figure out the intelligence of your
app just by watching the table design. One can watch what is going on
when data have been entered or updated but not _how_, and if someone
can figure it out, he will already know how to build a similar app
without knowing your table design.

/gustav


> If I'm reading the help file correctly, encryption does not hide the
> objects, just the data, yes?  I need to hide the design of the back end.
> Password protection is too weak.  I'll be up against professionals.

> Rocky

> ----- Original Message ----- 
> From: "Gustav Brock" <gustav at cactus.dk>
> To: "Access Developers discussion and problem solving"
> <accessd at databaseadvisors.com>
> Sent: Monday, June 21, 2004 9:41 AM
> Subject: Re: [AccessD] Hiding Back End Design


>> Hi Rocky
>>
>> You can encrypt the database. Not bulletproof, of course, but keeps
>> the average user away.
>>
>> /gustav
>>
>> > Is there a way to easily hide the back end design?  My distributor in
> Taiwan feels that if the back end design is not hidden then the product can
> be easily knocked off.