It seems that I too often need to duplicate a layout simply to have a version with a different behavior on one or more fields. And duplicate layouts are expensive to maintain. In the simplest case, it would be nice if I could control whether a field is enabled in browse mode or not.

Have you looked at Field Behaviour? Turn off entry in Briowse mode and Find mode.

I missed your response. I know about field behavior. The point is that I have to create two layouts to have a field sometimes enabled and sometimes not enabled for entry, rather than being able to control that with a script.

There are ways of controlling fields directly but it would depend upon the purpose here. For instance, are there certain privilege sets which should have access and others not? Or would it depend upon the value in another field?

For instance, if you can give up the ability to tab to the field, you can turn off entry via browse and attach a script directly to the field which, if certain conditions AREN'T met, will do nothing (no entry) but if the conditions are met, the button attached would be simple: Go To Field [ that field ]. You can also control access via privilege but, although I've played with that concept, I haven't used it extensively (it feels harsh to me).

Usually my 'field protect' scripts provide a message and look something like:

If [ 'whatever criteria not allowing entry' ]

Show Custom Dialog [ "Sorry but you can't" ]

Else

Go To Field [ that field ]

End If

LaRetta :wink2:

Edited March 8, 200718 yr by Guest
Added End If (blush)