Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Stored Procedures
Message
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00002945
Message ID:
00003107
Views:
31
>>What other solution is there? In a primary key
>>you should use a lookup such as a list box. In
>my
>>routine I catch the problem, inform the user &
>let
>>them either change the data or revert. What else
>>can you do with a Primary index?
>>
>>Tom
>
>But is checking in the valid event a good idea, or
>would a routine be called upon from a higher
>level?

Greg

Yes I was as clear as mud...

My procedure is in the SAVE routine -- a catch all.

The other response is more local. A Valid() is what I use because by returning FALSE the user is kept on the current object -- they do not advance to the next object. You can always call another procedure from the valid() if you want.

Tom
Tom
--------------------------------
Tom O'Hare
407-299-4268 -- tom@redtile.com -- http://www.redtile.com/
Independent Programmer Using Visual FoxPro, Visual Basic & more...
Operations Manager -- Virtual FoxPro User Group (VFUG)
http://www.vfug.org/ -- tom@vfug.org
President -- Central Florida FoxPro User Group (CFFUG)
http://www.redtile.com/foxpro/
Universal Thread Most Valued Professional (MVP)
http://www.transformation.com/foxpro/
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform