Storing Data Securely

  • Thread starter Thread starter TC
  • Start date Start date
T

TC

Answered under your other post.

TC


Kevin Seitz said:
(i think i posted this already but it never showed up in the newsgroup..
sorry if it is there twice)


Well, is there any other way to securely store data without using user-level
security? I would use a table but that can be linked/imported and edit by a
user.

I guess what I am mainly trying to do is set a trial version for a program
so that the user can use it for so long and then has to register. I found a
solution to this at http://www.logico-solutions.com/ . However, I am
deploying the database where installers aren't exactly good and probably
don't have references to all the codes I need.

Is there any way I could possibly write the values to a DLL or the registry
myself? Tell me if there is (a link to a site works good too) ANYTHING THAT
IS PARTIALLY SECURE WOULD WORK!!!! THANKYOU :-)
kevin
Click to expand...
 
(i think i posted this already but it never showed up in the newsgroup..
sorry if it is there twice)


Well, is there any other way to securely store data without using user-level
security? I would use a table but that can be linked/imported and edit by a
user.

I guess what I am mainly trying to do is set a trial version for a program
so that the user can use it for so long and then has to register. I found a
solution to this at http://www.logico-solutions.com/ . However, I am
deploying the database where installers aren't exactly good and probably
don't have references to all the codes I need.

Is there any way I could possibly write the values to a DLL or the registry
myself? Tell me if there is (a link to a site works good too) ANYTHING THAT
IS PARTIALLY SECURE WOULD WORK!!!! THANKYOU :-)
kevin
 
The short answer is no, there is no way to securely store data in an Access
solution. Even with user level security, you would need to understand that
there are easily available programs that will retrieve the usernames and
passwords used with secured apps. You can certainly write a registry value
(there is tons of code on the web showing you how to do this, so I won't
repeat it here), but that won't stop someone from stepping through your code
and determining where this value is and changing it. And, while you mention
references ... how can you insure that your remote users will have the same
references set? One bad reference and your ap doesn't run ... what do you do
then?

Tony Toews has an essay on deploying trial apps ... google on his name and
you'll find his site. Why will Paul's solution not work for you (or the one
TC gave you)?

Deploying Access apps is not easy ... it's full of pitfalls, dropped
references, and other troubles too numerous to mention. A good install
program goes a long way towards easing these troubles, but they are
generally expensive and require time to learn.
 
Back
Top