The basic approach involves keeping track of what customer is logged in and
then having the application only show him his/her records (based on a
customer ID in each record).
There are various ways to implement this -- it can be done in filters, it
can be done by adding a "where" clause in the SQL code that retrieves the
data (if you're using SQL), it can be done by adding a "where" clause in the
SQL that is the definition of the recordset to open, or it can be done as a
parameter to a query.
Whichever way you chose, the net result is that the customer has to validate
him/herself through a password in order to log in. Once the customer has
successfully logged in, you now know the customer ID. You then show the
customer only those records that have the customer's ID in them.
"Amateur" <(E-Mail Removed)> wrote in message
news:6948A0B5-B7B6-45AC-8AC8-(E-Mail Removed)...
> I have one table with different customer data in it. This table should
> support our customer web information. How can I protect that table so that
> the customers only get his information out of that table? - or better how
can
> I protect each record of the table for a different customer?
|
Similar Threads
