You could write your own PRG to validate all the tables in the DBC. I understand validating the views is a pain, but what if you have views that are now broken becuase a source table changed? In the PRG, you could initialize all the parameters for your views, that way SDT will not prompt you for their values when views are validated. If you take that approach, just add these parameters and values in the sample code below:

OPEN DATABASE MYDBC
SET DATABASE TO MYDBC
oMeta = NEWOBJECT("DBCXMgr", "DBCXMgr")
lnRetVal = ADBOBJECTS(laTables,"TABLE")
FOR EACH lcTable in laTables
    llRetVal = oMeta.Validate(lcTable, 'TABLE')
    if not llRetVal
       * validation of that table failed
    endif
ENDFOR

>Hi there,
>
>We use Stonefield in our application. Whenever any developer alters any fields in our database he is obliged to validate the metadata so coremeta is always up-to-date in our development environment.
>However, our DBC contains quite a lot op parameterised views. During the validation process, we have to click on the "continue" and "OK" messageboxes which are prompted by Stonefield about 60 times. This is REALLY tiresome and frustrating.
>Is is possible to make Stonefield skip all views during the vaildation process so we won't all become RSI victims. (we don't it to contain the views).
>
>Thanks,
>
>
>Geert van Snik
>Zorgned Automatisering
>Wageningen, the Netherlands