Very Computer

>Here's the desired sequence.  Two databases are related on a common field.  
>The second database follows the first.  Info from the second database is
>displayed based on the value in the common field in the first database.  I
>use a push button to select a new value for the first field from a POPUP,

>database, has not changed, despite the common field having changed.  Is that
>too confusing?  The code is not long, but this description is probably
>better.

>GETS or SHOW GET  to refresh the field.  However, it is undesirable to let
>the user have access to the displayed info (to change it) and I have already
>said that I don't like the looks of a disabled object.

>There you have it.  Suggestions will be gratefully and humbly received.  If
>you decide to mail a response directly to me, be advised that my mail
>handler is a lying machine.  Instead of using the address you see on your
>screen, the following is a sure-fire address:

>Thanks,
>Jim
>Standard disclaimer applies.

>Here's the desired sequence.  Two databases are related on a common field.
>The second database follows the first.  Info from the second database is
>displayed based on the value in the common field in the first database.  I
>use a push button to select a new value for the first field from a POPUP,

>database, has not changed, despite the common field having changed.  Is that
>too confusing?  The code is not long, but this description is probably
>better.

>GETS or SHOW GET  to refresh the field.  However, it is undesirable to let
>the user have access to the displayed info (to change it) and I have already
>said that I don't like the looks of a disabled object.

>There you have it.  Suggestions will be gratefully and humbly received.  If
>you decide to mail a response directly to me, be advised that my mail
>handler is a lying machine.  Instead of using the address you see on your
>screen, the following is a sure-fire address:

>Thanks,
>Jim
>Standard disclaimer applies.

>It is possible to change the disabled colors either globaly, using
>SET COLOR SCHEME or individualy for each GET, using a color list.

>>I am having a problem refreshing them once the screen is
>>painted and the info that should be displayed has changed.  I would like
>>some help figuring out how to do this.

>>Here's the desired sequence.  Two databases are related on a common field.
>>The second database follows the first.  Info from the second database is
>>displayed based on the value in the common field in the first database.  I
>>use a push button to select a new value for the first field from a POPUP,

>>database, has not changed, despite the common field having changed.  Is that
>>too confusing?  The code is not long, but this description is probably
>>better.

>>GETS or SHOW GET  to refresh the field.  However, it is undesirable to let
>>the user have access to the displayed info (to change it) and I have already
>>said that I don't like the looks of a disabled object.

>>There you have it.  Suggestions will be gratefully and humbly received.  If
>>you decide to mail a response directly to me, be advised that my mail
>>handler is a lying machine.  Instead of using the address you see on your
>>screen, the following is a sure-fire address:

>>Thanks,
>>Jim
>>Standard disclaimer applies.

>The screen builder in foxpro has an option to refresh output fields (i.e.
>SAY objects). I once looked at the .SPR generated program and saw that a UDF
>was invoked by one of the READ clauses. The UDF then redisplayed the SAY.
>Sorry to say but I can't remember which read clause it was (havn't got access
>to FOX right now). You can either experiment with the screen builder or look
>up READ in the manual.

>Hope this helps (e-mail if not clear),