Ok. I think that in VFP 3.0 AERROR function had a different behavior. I'll fix the bug myself. I chose Tastrade to have some tips how a real application works. Anyway, thanks, José Augusto Cavalcanti Global Connection jcavalcanti@ax.apc.org > >>Hi folks, >> >>I chose "Mastering Microsoft Visual Foxpro" CD and Tastrade sample >application >> to start learning VFP. >> >>I thought using Tastrade classes to develop a small application (just for >> learning purposes). >> >>When I was checking how Tastrade handles Field Rules Validation I got an >error. >> >>The steps : >>1 - Open the Employee form >>2 - Add a new record >>3 - Try to save this blank record >> >>Code : >>lcMessage = DBGETPROP(ALIAS() + "." + laError[3], "Field", "RuleText") >>lcMessage = STRTRAN(lcMessage, '"', '') >> >>Error : >>FUNCTION ARGUMENT VALUE, TYPE OR COUNT IS INVALID. >> >>Values : >>ALIAS() - EMPLOYEE >>laError[3] - "Last name cannot be empty." >> >>The code was waiting for a field name in laError[3], not the "RuleText" >itself. >>Is this bug fixed in 5.0a ? >> >Nope, it's still there. I don't think they upgraded/tested Tastrade much in >vfp5, I've seen at least one other bug. A more state-of-the-art project is >the Solution in vfp5... > >. >