Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Double-entry
Message
 
À
28/12/1999 07:11:36
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Titre:
Divers
Thread ID:
00308600
Message ID:
00309101
Vues:
27
Jeff,

To do what Cetin suggests you could try the following:

The first time they press OK, put someting like this in the code of the click event (actually, you should make it a form method and call it from the button's click)

WARNING - UNTESTED CODE
local loObject
for each loObject in thisform.Objects
  if upper(loObject.BaseClass) = 'TEXTBOX'
    loObject.Tag = tran(loObject.Value)
  endif
endfor
The second time they press OK, do the following
local loObject
for each loObject in thisform.Objects
  if upper(loObject.BaseClass) = 'TEXTBOX'
    if ! (loObject.Tag == tran(loObject.Value))
      * Raise the alarm!
      return .f.
    endif
  endif
endfor
Cheers,

Andrew

>How do I go about doing that? I'm still feeling my way through vfp 6.0
>
>TIA
>
>Jeff T.


If we were to introduce Visual FoxBase+, would we be able to work from the dotNet Prompt?


From Top 22 Developer Responses to defects in Software
2. "It’s not a bug, it’s a feature."
1. "I thought I fixed that."


All my FoxTalk and other articles are available on my web site.


Unless specifically identified otherwise, anthing posted here is purely my opinion and may or may not reflect the policies or practices of Microsoft.
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform