>>No didn't mean trouble :) Wanted to say I didn't reply before as I wasn't sure I understood :)
>>
>
>Thanks
>
>
>>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.
>
>I wanted to avoid per company stuff, I have had experience in FPD25 wasn't pretty, once bitten twice shy and plus I wanted to remove a distribution just becuase a company changed spec. eg. increased the no. of test bed to 20. And plus I wanted the guy installing the app at the user to get it done and over with. I develop individually and get guys to do support, can't get any VFP developers here all want to do .NET, SQLServer, etc. when the companies are not ready to increase cost of ownership, same everywhere I guess <g>
>
>>OTOH what you do should also work. I do similar in FoxyClasses EditGrid and directly query DBC for validation code.
>>Cetin

OK so you want to manage from another table as metadata. How about doing your way but changing default/validation for view once at a suitable place (typically when metadata is edited and saved).

ie : You could do like this :

open data myData
select metadata
scan
  lcViewField = trim(VievName -'.'-ViewFieldName) 
  DBSetProp(lcViewField,"FIELD","RuleText",FieldRuleText)
  DBSetProp(lcViewField,"FIELD","RuleExpression",FieldRuleExpr)
  DBSetProp(lcViewField,"FIELD","DefaultValue",FieldDefaultExpr)
endscan

Cetin