Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Different behavior when debugging
Message
De
01/02/2005 12:42:40
 
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Versions des environnements
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP SP2
Network:
Windows 2003 Server
Database:
Visual FoxPro
Divers
Thread ID:
00982681
Message ID:
00982748
Vues:
22
>Hi everybody!
>
>I have a situation in which the following piece of code behaves in different ways depending if I am debugging it(stepping through the lines of code) or not.
>
>
>* ZAP the table that holds the current configuration
>* New configurable items will be added.
>go_SQL.cmpA_tmpf14.m_Zap()
>WITH THISFORM
>  x_Loadbom(lcBomno, lcRevlev, lcLoctid, lcLintype, lnLevel, lnQtyUsd, .T.)
>  x_LoadCfgItems()
>  * GOTO TOP IN a_tmpf13
>  go_SQL.cmpA_tmpf13.m_MoveRecord(Cn_TopRec)
>  * GOTO TOP IN a_tmpf14
>  go_SQL.cmpA_tmpf14.m_MoveRecord(Cn_TopRec)
>  .grdCfg.refresh()
>ENDWITH	
>
>
>The form has a grid that doesn't get refreshed when running normally, but it is when I am debugging it. This grid should show changes made to its recordsource (a_tmpf14). What could be causing this behavior? Any clue? Any workaround?
>
>Thanks everybody!

try
  ....
  .grdCfg.setFocus
ENDWITH	
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform