Protecting Database Design

[Alex]

I have an app I developed for a client who wants to market it. It will be in
a runtime. The front end will obviously be easily protected but the back end
table design and relationships end up being open for viewing. What's the
best way to protect this part of it.

 

[Keith Wilby]

I have an app I developed for a client who wants to market it. It will be
in
a runtime. The front end will obviously be easily protected but the back
end
table design and relationships end up being open for viewing. What's the
best way to protect this part of it.

Hi Alex,

If you've "protected" the FE (I'm assuming with user-level security) then
why can't you apply this protection to the BE? Be warned that user-level
security can be hacked by someone with the rights tools and some
determination, it isn't bomb proof.

Keith.
www.keithwilby.com

 

[Alex]

I made the front into an mde prior to setting up the runtime. I have not put
any security into the app beyond that at this point. Setting security would
still allow the user to see the relationships (I think) which is what I was
trying to prevent.