challenge from the peanut(s) gallery

[yafreax]

Tricky. . .

I have 2 files. File A -> File B based on KeyField; Allow Creation of related records.

In FileA i have a layout which contains a Portal for File B. Within this portal is FieldB [Number field]. I need to be able to restrict the user to only entering a number once. After FieldB is exited, it must "lock" itself, so that it cannot be re-edited without the Admin's intervention.

I have seen this done in a single file solution, but i lost my hard drive about 2 weeks ago and know not where to look to get any ideas from. . . any workarounds for a relationship solution?

TIA

Jeremy

[yafreax]

tooooo easy. . .

i spend too much time thinking about football and music and not enough time sharpenin' my skills anymore. . .

6 months ago i could've had that in about two secs. . . just bein' lazy today i guess. . . it's monday. . . had to recap all the weekend's action . . .

thanks for showing me. .. that'll work fine ( i've used a method like this before, i guess i really am being lazy today!)

Jeremy

[Rigsby]

There are about 20 different ways to do this! Some elegant, some not! Some fast, some not. One way – fast, effective and looks good is to use a script. Set the field as a button with a script that basically says, if fieldB empty go to fieldB otherwise show message, with something like “Sorry! You can’t edit this field”

PS: There are some more efficient ways to deal with this, but I like this way, as it allows a message! You can also allow the user to change the field (If he/she has made a mistake) but record their actions if they choose to edit the value!

Rigsby