>Cetin
>
>>Looking as per your request. Honestly read before but didn't understand what you're trying to do.
>
>Sorry didn't mean to be a drag, but I know you had the experience and we were going through a thread, so I guessed I'd personally point it to you.
>
>>Sounds like AfterNew() is filling the new record with defaults. And sounds textbox.valid is validating the content, right ?
>
>Exactly
>
>>If so why not directly edit view to have these defaults, validations and validationtext. You could write a developer tool (prg) to get these defaults and validation from base table(s) and put into view properties. To me it seems to be easier to do a series of dbgetprop()/dbsetprop(). Or directly use 'Properties' button of designer (if you're using the designer), still would be easier, no?
>
>I have this app this can be used in the same industry, but some of the specs like no. of the test beds for engines, which will vary from company to company, plus default values of RPM of engines etc. will vary again. So the idea here was to sell it again and again <g>. I wanted to reduce work between companies in ditribution as it is still in a jello mode and modules will keep on changing for atleast 6/8 months.
>
>The fixed specs I can freeze into the app and DBC's.
>
>Thanks for the trouble.
>
>
>Sincerely.

No didn't mean trouble :) Wanted to say I didn't reply before as I wasn't sure I understood :)

OK you want to create different default, validations per company. Still wouldn't a programmatically view creation answer your problem. You compile one view 'creator' per company.
OTOH what you do should also work. I do similar in FoxyClasses EditGrid and directly query DBC for validation code.
Cetin