>>May be I am missing something, but why you try MODIFY View? Just repeate: create view ... with the new definition. It will replace previous view definition in the DAtabase.
>
>The view is paramaeterized. Stepping through the view designer takes longer too.

Huh? Why does parameterization present a problem? Can you use something like this?

local array ladatabases[5]
ladatabases[1] = 'Database1'
ladatabases[2] = 'Database2'
ladatabases[3] = 'Database3'
ladatabases[4] = 'Database4'
ladatabases[5] = 'Database5'
lcsqlstr = space(0)
for lxx = 1 to alen(ladatabases)
   lcsqlstr = [create sql view MySQLView] + transform(lxx) + [ remote ] +;
      [select tab1.field1, tab2.field2 from ] + ladatabases[lxx] + [.dbo.Table1 tab1, ] +;
      ladatabases[lxx] + [.dbo.Table2 tab2] + ;
      [ where tab1.PK = tab2.FK and tab1.field2 = ?lusomevalue ] +;
      [order by 2]
      &lcsqlstr
endfor

You could also add the appropriate DBSetProp() commands after the macro expansion.

HTH.