Block fields to avoid accidental modifications?

[K3lso]

How can I block the fields so the only way to insert or edit data is to click on a EDIT BUTTON or something like that would allow me to do that?

[K3lso]

How can I block the fields so the only way to insert or edit data is to click on a EDIT BUTTON or something like that would allow me to do that?

[K3lso]

How can I block the fields so the only way to insert or edit data is to click on a EDIT BUTTON or something like that would allow me to do that?

[dwins]

Duplicate the layout. Have first layout uneditable but with an "Edit" button that takes you to the editable layout, and a lock button that takes you back to the first.

[dwins]

Duplicate the layout. Have first layout uneditable but with an "Edit" button that takes you to the editable layout, and a lock button that takes you back to the first.

[dwins]

Duplicate the layout. Have first layout uneditable but with an "Edit" button that takes you to the editable layout, and a lock button that takes you back to the first.

[sbg2]

Block all fields or just a few fields?

[sbg2]

Block all fields or just a few fields?

[sbg2]

Block all fields or just a few fields?

[stanley]

Your choice, really.

For example: when a user clicks on a "create new record" button (or whatever) you take them to a layout that allows them to enter data in the record. When they go to view the record later, they are taken to a layout which they cannot enter data into (or which they can only enter supplementary data into), unless they click on a button which *unlocks* the fields, in which case you take them to a layout where they can edit the data... It's all a matter of using layouts to fool the user into thinking they're always on the same layout. They may LOOK the same, but they are not in fact the same.

-Stanley

[stanley]

Your choice, really.

For example: when a user clicks on a "create new record" button (or whatever) you take them to a layout that allows them to enter data in the record. When they go to view the record later, they are taken to a layout which they cannot enter data into (or which they can only enter supplementary data into), unless they click on a button which *unlocks* the fields, in which case you take them to a layout where they can edit the data... It's all a matter of using layouts to fool the user into thinking they're always on the same layout. They may LOOK the same, but they are not in fact the same.

-Stanley

[stanley]

Your choice, really.

For example: when a user clicks on a "create new record" button (or whatever) you take them to a layout that allows them to enter data in the record. When they go to view the record later, they are taken to a layout which they cannot enter data into (or which they can only enter supplementary data into), unless they click on a button which *unlocks* the fields, in which case you take them to a layout where they can edit the data... It's all a matter of using layouts to fool the user into thinking they're always on the same layout. They may LOOK the same, but they are not in fact the same.

-Stanley

[K3lso]

If I duplicate the layout and block it, the new duplicated layout is automatically blocked too.

[K3lso]

If I duplicate the layout and block it, the new duplicated layout is automatically blocked too.

[K3lso]

If I duplicate the layout and block it, the new duplicated layout is automatically blocked too.

[Gabe]

Unlock them on the new layout after you duplicate it :P

[Gabe]

Unlock them on the new layout after you duplicate it :

[Gabe]

Unlock them on the new layout after you duplicate it :

[K3lso]

The thing is... If I duplicate a layout, the the new duplicated one isn

[K3lso]

The thing is... If I duplicate a layout, the the new duplicated one isn

[K3lso]

The thing is... If I duplicate a layout, the the new duplicated one isn

[bikergeek]

You can block all the fields on a layout, or just specific ones, by using one script and an extra field.

Define a button for all the fields you want to lock, and have the button run a script, using as a parameter the name of the field clicked:

If [lockField = "locked"]

Exit Script

Else

Go to Field []

Loop

Exit Loop If [ get(active FieldName) = get(ScriptParameter) ]

Go to field [Next]

End Loop

End If

You can then create a "Lock" button which toggles the value of lockField between "locked" and "unlocked".

Duplicating the layout is unnecessary.

[bikergeek]

You can block all the fields on a layout, or just specific ones, by using one script and an extra field.

Define a button for all the fields you want to lock, and have the button run a script, using as a parameter the name of the field clicked:

If [lockField = "locked"]

Exit Script

Else

Go to Field []

Loop

Exit Loop If [ get(active FieldName) = get(ScriptParameter) ]

Go to field [Next]

End Loop

End If

You can then create a "Lock" button which toggles the value of lockField between "locked" and "unlocked".

Duplicating the layout is unnecessary.

[bikergeek]

You can block all the fields on a layout, or just specific ones, by using one script and an extra field.

Define a button for all the fields you want to lock, and have the button run a script, using as a parameter the name of the field clicked:

If [lockField = "locked"]

Exit Script

Else

Go to Field []

Loop

Exit Loop If [ get(active FieldName) = get(ScriptParameter) ]

Go to field [Next]

End Loop

End If

You can then create a "Lock" button which toggles the value of lockField between "locked" and "unlocked".

Duplicating the layout is unnecessary.

[Ender]

I'm with dwins. I use one layout with the fields editable, and a duplicate layout with the field behavior changed to not allow entry into the fields. Scripts then control access to the edit layout.

The thing is... If I duplicate a layout, the the new duplicated one isn

[Ender]

I'm with dwins. I use one layout with the fields editable, and a duplicate layout with the field behavior changed to not allow entry into the fields. Scripts then control access to the edit layout.

The thing is... If I duplicate a layout, the the new duplicated one isn

[Ender]

I'm with dwins. I use one layout with the fields editable, and a duplicate layout with the field behavior changed to not allow entry into the fields. Scripts then control access to the edit layout.

The thing is... If I duplicate a layout, the the new duplicated one isn

[bikergeek]

The one significant advantage I can think of that a separate layout has over a scripted single layout is better control over the ability to tab from field to field or not.

Using scripted fields, you can still tab into a field without activating the script.

[bikergeek]

The one significant advantage I can think of that a separate layout has over a scripted single layout is better control over the ability to tab from field to field or not.

Using scripted fields, you can still tab into a field without activating the script.

[bikergeek]

The one significant advantage I can think of that a separate layout has over a scripted single layout is better control over the ability to tab from field to field or not.

Using scripted fields, you can still tab into a field without activating the script.