![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I need to add a record to a table; one of the fields in the table is the user_id. When I try to use the insert record server behavior, there is no way to select the user_id session variable! How is this done? |
#3
| |||
| |||
|
|
I need to add a record to a table; one of the fields in the table is the user_id. When I try to use the insert record server behavior, there is no way to select the user_id session variable! How is this done? Use a hidden variable in the form, and assign it the value of the session. |
#4
| |||
| |||
|
|
to select the user_id session variable! How is this done? Use a hidden variable in the form, and assign it the value of the session. And what if the user manipulates that value? Hidden form fields _always_ require a validation on the server. One purpose of a session is to avoid that sensitive data is sent to the client, where it can be manipulated. |
#5
| |||
| |||
|
|
to select the user_id session variable! How is this done? Use a hidden variable in the form, and assign it the value of the session. And what if the user manipulates that value? Hidden form fields _always_ require a validation on the server. One purpose of a session is to avoid that sensitive data is sent to the client, where it can be manipulated. Exactly how is the value of a SESSION VARIABLE manipulated by the client? |
#6
| |||
| |||
|
|
Exactly how is the value of a SESSION VARIABLE manipulated by the client? It can be manipulated if it's put into a hidden form field. |
#7
| |||
| |||
|
|
Exactly how is the value of a SESSION VARIABLE manipulated by the client? It can be manipulated if it's put into a hidden form field. You don't know what you're talking about. |
#8
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |