By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,705 Members | 1,845 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,705 IT Pros & Developers. It's quick & easy.

Securing a Backend

P: n/a
G'day, The derivation of a (commercially valuable) relational schema has
taken me a considerable amount of time. Now I want to secure the design in
a client server environment. Hence to my question: How have developers
successfully prevented access to their data tables and protected their
database design?

Looking forward to some suggestions.
Tony
Nov 13 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
On Wed, 25 Aug 2004 01:02:23 GMT, "Tony" <ri*********@hotmail.com>
wrote:

Access (better: Jet) is not a client/server database.
To secure a Jet database you have to understand there are cheap
password crackers available. If you are not too concerned with them,
then download, study, and fully understand the Access Security FAQ
from microsoft.com. You'll learn that it is indeed possible to
disallow anyone but your application access to the back-end tables.

Personally I would not put too much value on a database design. The
commercial value is likely not in the db design, but in the
application using it. Keep the db open for your clients to access it
as well, to create ad-hoc reports etc.

-Tom.

G'day, The derivation of a (commercially valuable) relational schema has
taken me a considerable amount of time. Now I want to secure the design in
a client server environment. Hence to my question: How have developers
successfully prevented access to their data tables and protected their
database design?

Looking forward to some suggestions.
Tony


Nov 13 '05 #2

P: n/a
"Tony" <ri*********@hotmail.com> wrote:
How have developers
successfully prevented access to their data tables and protected their
database design?


*First* read and understand this:

<http://support.microsoft.com/default...access%2fconte
nt%2fsecfaq.asp>

You can then deny user access to your tables if you base all of your forms
& reports on queries with 'owner' access. Of course you can also hide the
db windoow and close the 'back door' methods of unhiding it.

You can also check out my step-by-step example on securing an Access app on
my web site (there's all sorts of junk on there, use the LH nav panel to
navigate to the Access area).

Regards,
Keith.
www.keithwilby.org.uk
Nov 13 '05 #3

P: n/a

"Keith Wilby" <ke*********@AwayWithYerCrap.com> wrote in message
news:Xn************************@10.15.188.42...
Regards,
Keith.
www.keithwilby.org.uk

Keith--

Is that a naked picture of you on your Web site, or do I need to adjust my
color?

--JW
Nov 13 '05 #4

P: n/a
"John Wilde" <wi******@hotmail.com> wrote:
Keith--

Is that a naked picture of you on your Web site, or do I need to adjust
my color?


Erm, adjust your colour, the picture may be naked but I'm not ;-) I've been
meaning to change that photo for a while. It was taken on holiday in
Florida and I can assure you I have shorts on!
Nov 13 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.