I'm having a frustrating time. We are trying to create Foxpro remote views to a SQL Server database that we upsized to. We are trying to create the remote views similar to the old views we had so as not to require much change to our programs. It seems as though Fox tries to evaluate the views from a Fox perspective instead of a SQL Server perspective before it will let me save anything. For example. In our old views, we used the NVL() function. In the new remote views I try to use the SQL Server IsNull() function. When I try to save the view, it says that I have 'too many arguments'. It's trying to evaluate the IsNull() function as if it were the Fox IsNull() function. (In Fox IsNull(.null.) = true, in SQL Server IsNull(.null., 'Bill') = 'Bill') I've verified that what I'm entering is correct for SQL Server in the query analyzer. Anybody else ran into this? In addition, in our old views we used IIF() functions. In SQL Server, I'm trying to use CASE(T-SQL). Again, I verified that it worked in the query analyzer. In this case, after I create the expression, when I click the button to move the expression onto the fields side of the view screen, Fox automatically puts double-quotes around my expression. Then when I try to save the view, it says the 'column is not found'. My understanding is that it thinks it should be a column because it is surrounded by double-quotes. But I cannot get Fox to not put them there. Again, anybody encountered and overcome anything like this?