access database security

[andrewbadera]

what can I do to "lock down" an access database? I have an access database deployed to a client website with a third-party ISP; I suspect they'd like to try and resell the solution I'm writing for them, and that's something I'm fine with, just so long as I get a royalty or cut of some sort. so, I can't leave this database completely accessible to just anybody, what's the proper procedure to lockdown an access mdb file with an ODBC DSN deployed on a third party ISP host for use in a web application?

 

[RickSpr]

I would think the main thing would be to protect your code and perhaps design details of queries, forms, and reports. Creating an MDE will do that. (Remember to keep your design copy MDB file!)

There might possibly be some issues with running an MDE with web access, but I doubt it. Rick Sprague

 

[andrewbadera]

from what I understand, the mde file still leaves tables and etc. viewable ... my code will be encapsulated in COM objects, so all I'm worried about protecting is access to data and table structures in general ...

 

[RickSpr]

Ah. I didn't understand that you wanted to hide the table data. (Can't say I really understand wanting to do this, but I don't design web applications so I'll take your word for it.)

I'm afraid this is over my head. But now that I've posted here and there are some replies, the experts you need may not look at this thread, thinking it's been addressed. If nobody else comes to your aid in the next day or two, try posting it again. Threads with no replies attract more attention.

You might also find help in other forums, such as web design and ASP-related forums. Sorry I couldn't be more help. Rick Sprague

 

[andrewbadera]

thanks for your efforts ... my intention is to prevent the resale of my database and application ... if my code's encapsulated in COM objects, I don't have to worry about protecting souce so much, but I do still have to worry about them duplicating the database. the more I can deny access to, the less likely they'll be able to resell my solution without my say-so.

 

[Guest_imported]

Rochester,
I am facing same problem as you are facing. I have tryed several solutions but nothing worked. Hope we will found out some thing from this thread.

 

[mikemcginty]

I have the same problem, which is worse when my user has to have Admins membership in order to Compact the database.

i am using a VB front end so most of the protection is employed there. I would like to do something about some of the tables though.

I created my database according to MS guidelines to give user-level security. I found that the security is non-existent if I link the DB to another unprotected workgroup file.

Mike When you call out for help in the darkness, and you hear a voice in return, you're probably just talking to yourself again!