>>I see, spprice is to reflect the 'Current' particular item price for particular
>>client.
>>But the Orderline contain price will be the Real price for print-out.
>>
>>Actually there will be fine if my boss don't ask for security control!!
>>
>>Owing to price control, only manager or ppl having the password can edit the
>>price! So, the sales will hard to fill the orders on form... Quite inefficence.
>>
>>Secondly, as my company want to fit the ISO and need confirmation on Update
>>and Add!! ~~~>_<~~~
>
>Justok,
>
>All you have to do is never expose the price field in the orderlines for editing and restrict the spprice table to be only edited by authorized people. If the price field from orderlines is alwasy only read only, there is no security problem. You can create global vaiable in your application name OkToEdit adn then make the Field Validation rule for every field of every table OkToEdit AND Whatever(), where Whatever() is any other validation you might need.
>
>This way any attempt to open the tables without running your application will result in a error at every attempt to update any value anywhere.
>
>So, there your security is fixed :-)

Currently, I use a staff.dbf to hold the staff info include Title and password.

Then, according to title, there is a main form(non-kill controlcenter)
to hold the value of Title! ^_^;

Then, Check Title for right or not... But got problem if user just edit
some field and move to another records....
More than 2 ways to do, use nevigator bar to next record, or select the combox
of Primary key ...
The last one make me more uncertain is the links will call the record pointer
move unexpectively.. >_<"