Chipp,

Thanks for the advice, I will have a think about all the various comments and see what seems the most secure approach. If we go ahead I may bounce the proposed structure of this list again.

Regards to all

John T

Chipp Walters wrote:
John,

Here's how I solve a similar problem.

I ask the user to login with a name and a password. They enter it and
it goes (securely) to a web page on a server, There the connection is
made to the database passing along the username and password for
verification. This way there is never a need to store anything but the
address of the webpage in the client app. No users or passwords are
ever stored there.

best,
Chipp
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to