Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Problems with INDEXSEEK()
Message
De
19/08/2000 09:14:41
 
 
À
19/08/2000 09:01:17
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Divers
Thread ID:
00406838
Message ID:
00407021
Vues:
56
>Hope you caught my reply about FILTER doing me in. I do agree about making this uneditable for an existing record, and will change it accordingly. Are you saying I only need "!!!!!!!!!!!!!!!" in the Format property? And blow away the Input Mask? I still need to allow anything, including 0-9, - , *, etc. This input and display formatting has always been a confusing issue for me since the 2.X days. The Help and the Hacker's Guide aren't very informative either. I seem to get a solution that works only through a lot of trial and error. Thanks again.
>

No, in the InputMask; there's no need for a separate format to get the uppercase character functionality, and there are no character restrictions "X" vs "!" in the InputMask.

MaxLength set to 15, InputMask set to =REPL('!',15), Value set to =SPACE(15) if not bound to a field which would init it IAC.

It's worked this way since the InputMask and Format were distinguishable - prior to VFP, InputMask was the PICTURE clause of an @...whatever; InputMask specifies character by character behavior, while Format specifies behavior for the entirety of the item.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform