The reason it's so noticeable is that after leaving an element it is changed to a different color than it was as a GoTo element. It's obivous that the focus is back in the last element.

Good morning all,
  Well, after giving it some thought in bed last night, I decided to use my previous day's database and start from scratch, ensuring I was ONLY working on the @Color and GoTo commands.

  I've entered my specs in the On Element Immediate Change section, which works well until I get to my @Calendar field. If I put the programming statement in On Element Immediate Change all I get is the date I selected, no color change and no GoTo response. I moved my programming to the On Element Entry section and get the desired result of the date selected, color change of the element, color change of the next element, and I've "gone to" that next element. However, again when I select the down-arrow on the combobox I get booted back to the element with the Calendar. I've made no program changes in the element I had hope to be in. (I did a Preview Application after every individual programming change in each element to verify I was getting the desired results.)

Ideas or thoughts?
Thank you,
Fred

It doesn't seem to be an issue with @UserSelect. I repeated the scenario of //-ing out all programming except the color and goto commands. Same result. The program passes through the element changing it to yellow with the next element green. When I click on the green element I'm returned to the yellow one. In this second scenario I'm going Text-to-Text elements, in the first Date-to-Text. I don't think that really matters. These are the only two elements on the form behaving in this manner.

Gee - had to happen on Labor Day weekend when no one is around to bounce this off.

At least I'm no longer having the issue of those two elements changing colors when I F10  through a retrieved record set. 

Hi Bob, thanks for an idea I hadn't thought of. Unfortunately this made no difference.

I also made a backup copy, added two new text fields, copied all the information from the original elements into the new elements, copied the programming, deleted the old elements, saved, renamed new elements with old elements names - same problem.

This is really pointing to a programmin glitch, but there's virtually nothing in either element.

Element: Priority (On Element Entry)

If @IsNew then
Priority = @popupmenu("High - Safety Issue, Impacts Quality or High Eficiency Loss; Medium - Some Efficiency Loss or Chronic Occurence; Low - Nice To Do", "Choose Priority") 

Priority - (On Element Immediate Change)

If @lt(Priority,3) = "Low" then Priority = "Low"
If @lt(Priority,3) = "Med" then Priority = "Medium"
If @lt(Priority,3) = "Hig" then Priority = "High"

If @add then
{
  @Color(Priority,0,14)
  @Color(Owner,15,2)
  GoTo Owner
  
} 

Element: Owner - (On Element Immediate Change)

var vName as String
vName = Owner

If @UserID = "mgr" then
{
LE45 = vName
Assigned_by = @UserID
}

If @add then
{
  @Color(Owner,0,14)
  @Color(Type,15,2)
  GoTo Type
} 

That's it - no other programming for either element - verified for what seems a million times. As I stated earlier, the Priority element changes to yellow and displays the correct results, the Owner Element changes to green and Focus appears to be in the element. When I click the down-arrow - right back to Priority I go until I select the down-arrow in Owner a second time.

I've also tried ThrowFocus and even included a double GoTo - all to no avail.

Fred
P.S. Nice to see SOMEONE in here this weekend besides me  

No, hadn't read it that way and no, hadn't tried it - but you did make me think of something (both of you) - since I have to click the down-arrow key anyway to bring up the choices in the combo box - why use GoTo at all???? Why not just change the color to lead the user where to click next? DUHHHHHHHH ROFLMAO

I knew it was too easy. That resulted in my having to double-click to get the selections in the combobox to appear. I'll try the navigation order - tomorrow at home on my DAY OFF 

Thanks for the ideas!

Glad it worked.

I usually use Navigation Order, but I thought perhaps maybe the order was no longer correct.  I have found that after the order was set, I might move some elements and forget to make changes to the defined order.

So, even though this might be OK now, we still don't know what was wrong.  Was the defined order wrong when you looked at it and needed to be changed?  Just curious, always like to know the cause of the problem, not just the solution.