I believe the documentation is incorrect and the color change is until the form is closed and re-opened. Add an Else statement to your If statement that changes the colors back.

-Ray

Ray -

I'm still having a problem that I don't understand.  First, here's the coding I am currently using.

If not @isblank(Alt ID)
then
RGBColor(Alt Record,0,0,0,0,255,0)
Else
RGBColor(Alt Record,-1,-1,-1,236,233,216) 

Here's what happens when I test it:

I retrieved a group of 8 records. 

Records #6 and #8 have an entry in the alt ID field.

I start on record #1 and advance through each record.  When I get to record #6 (which has an entry in the Alt ID), nothing happens.

When I get to record #7 (with a BLANK Alt ID), the command button changes color.

When I get to record #8 (which has an entry in the Alt ID), the button changed back to the "original" (incorrect, since there's an entry) color.

When I Alt/Tab to continue this message and then alt/tab back to record #8, the color has been changed to reflect the entry in the Alt/ID field.

When I "reverse" to record #7, the command button is the wrong color.

If I click anywhere on the form, the command button changes to the correct color.

I double checked to be sure that my programming was in the "on form ENTRY" (rather than "on form EXIT") and it is.

Now what?

By the way I tried the programming in both the Alt ID field and the command button field, but that made no difference.

The only thing I can think of trying (which I haven't yet) is to add a "throw focus" command.  I don't know whether that will do it or not but - even if it does - I don't understand why it should be necessary.

Ray -

I've said it before, and I'll say it again:


Now, I wonder how I would have known about forceredraw, though.  Might it not be a good idea to include it in the program documentation, in those cases where it is most likely to be needed?

I did read the documentation on forceredraw but it is not real specific.

Also, as an aside, I noticed the next command was forcecommit - something I may have use for and will have to "play" with next.  There's just no end to this learning process another good reason for Erika to get to the Tampa area, QUICKLY!  lol

Bob -

I'm surprised to think that the programming would have been used to "permanently" change the color for as long as the databse was open - since the documentation did say othersise.

I would, though, be very interested in hearing of the type of application and circumstances when it might be wanted.

Not withstanding that, I still think programming for a "temporary" change of color would still be valuable.  Sooooo, instead of CHANGING the existing command (if indeed it is determined not to be feasible) then I thnk that a NEW command (such as @colorrecord or @colortemp) should be made available to work as described.