Information générale
Titre:
Did Grid.SetFocus( ) Behavior Change in VFP7?
Hi, all!
We've been testing some of our larger applications in VFP7 for the past few weeks.
Here is a bug which I do not fully understand:
We have a grid on a form. The grid is based on one of our Grid Classes (grdBase).
grdBase Has a non-default SetFocus( ) method which moves the record pointer, depending on some properties of the form. All works well in VFP3, 5 & 6.
In VFP7, the SetFocus( ) method seems to be changing the selected ALIAS. This is causing the moving of the record pointer to fail. It wouldn't be so bad, except that sometimes we try to move to a record which doesn't exist in the table open in the newly acquired work area. That's when we get ERRORS.
I tried overriding the setfocus( ) in the grid on my form with:
SELECT cTempBuyr
IF !DODEFAULT( )
RETURN .F.
ENDIF
If I suspend in the first line of the default SetFocus, the alias selected is *NOT* cTempBuyr. It is the alias to which the grid is bound. Bizarro Maximo.
Anyone else seeing flakiness in the Grid's SetFocus( )? Did M$FT create this bug in my code by design? I couldn't find anything in the VFP7 Help File which mentions changing the behavior of this object.
Just wondering.
- George [Scratching my head as the client gets more and more impatient.]
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement