Hide contents of field...

[J.P.]

Hello,

I don't know how this can be done...

Is it possible to have users enter information when field is empty and hide the contents from after?

Thank you.

[J.P.]

Hello,

I don't know how this can be done...

Is it possible to have users enter information when field is empty and hide the contents from after?

Thank you.

[J.P.]

Hello,

I don't know how this can be done...

Is it possible to have users enter information when field is empty and hide the contents from after?

Thank you.

[dkemme]

I wonder if it would work to put a second copy of the field right on top of the first, use the first one to enter the data, have the second one to present the data, but set the text color same as the background of the layout. The trick will be to only allow data entry in the first one, not the second one, and to get the second one on top of the first.

[dkemme]

I wonder if it would work to put a second copy of the field right on top of the first, use the first one to enter the data, have the second one to present the data, but set the text color same as the background of the layout. The trick will be to only allow data entry in the first one, not the second one, and to get the second one on top of the first.

[dkemme]

I wonder if it would work to put a second copy of the field right on top of the first, use the first one to enter the data, have the second one to present the data, but set the text color same as the background of the layout. The trick will be to only allow data entry in the first one, not the second one, and to get the second one on top of the first.

[spb]

I can think of three ways (using FM 6, so there may be a 7 wrinkle I'm not aware of).

They both depend on how your user arrives at the field. If they begin on another layout, then click a button that navigates them to the layout with the field, then it's easy. Make a duplicate of the layout and remove the field from the duplicate. Set up your navigation scripts to test if the field is empty or not. Something like:

If (IsEmpty[Field])

Go to Data entry layout

else

Go to Field removed layout

EndIf

If this isn't practical, you could make a container field and place it on top of the field. Make the container field a calc field. The calc would be to set the container field to a previously stored global container field containing a few pixels of image the same color as your background. Set this if the entry field is not empty. The field will seem to disappear.

But you would have to script the user into the entry field, as they would click on the transparent container field on top of it. (a button running a one-line script, "Go To Field")

Finally, you could set the field up with a validation so that if it is not empty, alteration is forbidden. You get annoying error boxes this way, though.

Steve Brown

[spb]

I can think of three ways (using FM 6, so there may be a 7 wrinkle I'm not aware of).

They both depend on how your user arrives at the field. If they begin on another layout, then click a button that navigates them to the layout with the field, then it's easy. Make a duplicate of the layout and remove the field from the duplicate. Set up your navigation scripts to test if the field is empty or not. Something like:

If (IsEmpty[Field])

Go to Data entry layout

else

Go to Field removed layout

EndIf

If this isn't practical, you could make a container field and place it on top of the field. Make the container field a calc field. The calc would be to set the container field to a previously stored global container field containing a few pixels of image the same color as your background. Set this if the entry field is not empty. The field will seem to disappear.

But you would have to script the user into the entry field, as they would click on the transparent container field on top of it. (a button running a one-line script, "Go To Field")

Finally, you could set the field up with a validation so that if it is not empty, alteration is forbidden. You get annoying error boxes this way, though.

Steve Brown

[spb]

I can think of three ways (using FM 6, so there may be a 7 wrinkle I'm not aware of).

They both depend on how your user arrives at the field. If they begin on another layout, then click a button that navigates them to the layout with the field, then it's easy. Make a duplicate of the layout and remove the field from the duplicate. Set up your navigation scripts to test if the field is empty or not. Something like:

If (IsEmpty[Field])

Go to Data entry layout

else

Go to Field removed layout

EndIf

If this isn't practical, you could make a container field and place it on top of the field. Make the container field a calc field. The calc would be to set the container field to a previously stored global container field containing a few pixels of image the same color as your background. Set this if the entry field is not empty. The field will seem to disappear.

But you would have to script the user into the entry field, as they would click on the transparent container field on top of it. (a button running a one-line script, "Go To Field")

Finally, you could set the field up with a validation so that if it is not empty, alteration is forbidden. You get annoying error boxes this way, though.

Steve Brown

[Ted S]

Perhaps you could enter the info into a global field - by using a Custom Dialog box for instance - and then write the contents to the permenant field with a script that would clear the global field as the last step.

[Ted S]

Perhaps you could enter the info into a global field - by using a Custom Dialog box for instance - and then write the contents to the permenant field with a script that would clear the global field as the last step.

[Ted S]

Perhaps you could enter the info into a global field - by using a Custom Dialog box for instance - and then write the contents to the permenant field with a script that would clear the global field as the last step.

[LaRetta]

You can also use portal trick whereby an empty text field creates a self-join relationship but when it contains text the relationship breaks thus the portal (and text field) disappears.

I display entire groups of fields depending upon what is selected in another field, ie, if Company is Wholesale there may be an additional six fields which should be filled in. Instead of expecting Users to ignore those fields when Company is Retail, I place them all within one breakable portal.

I still use it and maybe this is 'prior 7 thinking' but a UniqueID matched to a HideText text field (Auto-Enter calculation, Replace) = If(IsEmpty(text); UniqueID) can make a one-line portal (containing your text field) appear and disappear. Just make the portal barely larger than the field(s) you wish to hide. And make your portal transparent line and fill pattern.

It doesn't matter which direction you wish to relate them because both fields can be indexed. These breakable portals can be based upon multiple criteria to determine which fields to show (and when). The Main file/table text field wouldn't even be on the layout - only the portal containing selfjoin::text and that is what they would type into - that is, if the relationship is valid and it shows.

This would save duplicating your layout (which wastes resources and is difficult to keep in synch with the original) but you will need some layout or view which displays the Main file/table field in case it needs REAL modification - or if your User goofs.

[LaRetta]

You can also use portal trick whereby an empty text field creates a self-join relationship but when it contains text the relationship breaks thus the portal (and text field) disappears.

I display entire groups of fields depending upon what is selected in another field, ie, if Company is Wholesale there may be an additional six fields which should be filled in. Instead of expecting Users to ignore those fields when Company is Retail, I place them all within one breakable portal.

I still use it and maybe this is 'prior 7 thinking' but a UniqueID matched to a HideText text field (Auto-Enter calculation, Replace) = If(IsEmpty(text); UniqueID) can make a one-line portal (containing your text field) appear and disappear. Just make the portal barely larger than the field(s) you wish to hide. And make your portal transparent line and fill pattern.

It doesn't matter which direction you wish to relate them because both fields can be indexed. These breakable portals can be based upon multiple criteria to determine which fields to show (and when). The Main file/table text field wouldn't even be on the layout - only the portal containing selfjoin::text and that is what they would type into - that is, if the relationship is valid and it shows.

This would save duplicating your layout (which wastes resources and is difficult to keep in synch with the original) but you will need some layout or view which displays the Main file/table field in case it needs REAL modification - or if your User goofs.

[LaRetta]

You can also use portal trick whereby an empty text field creates a self-join relationship but when it contains text the relationship breaks thus the portal (and text field) disappears.

I display entire groups of fields depending upon what is selected in another field, ie, if Company is Wholesale there may be an additional six fields which should be filled in. Instead of expecting Users to ignore those fields when Company is Retail, I place them all within one breakable portal.

I still use it and maybe this is 'prior 7 thinking' but a UniqueID matched to a HideText text field (Auto-Enter calculation, Replace) = If(IsEmpty(text); UniqueID) can make a one-line portal (containing your text field) appear and disappear. Just make the portal barely larger than the field(s) you wish to hide. And make your portal transparent line and fill pattern.

It doesn't matter which direction you wish to relate them because both fields can be indexed. These breakable portals can be based upon multiple criteria to determine which fields to show (and when). The Main file/table text field wouldn't even be on the layout - only the portal containing selfjoin::text and that is what they would type into - that is, if the relationship is valid and it shows.

This would save duplicating your layout (which wastes resources and is difficult to keep in synch with the original) but you will need some layout or view which displays the Main file/table field in case it needs REAL modification - or if your User goofs.