>Thanks Tamar.
>
>On the first item, I searched the help file for varchar(max) but did not find anything. Is that what you were meaning?

varchar(max) is SQL Server data type, not VFP one.
You can use it instead of MEMO. But be careful when you use it. SPT will not recognize this type and always will give you empty field.
You should use CursosAdapter with Cursorschema set.



>
>Regarding large tables, I had thought about that - the current app allows users to browse and do incremental search on the key tables but that will probably have to go away. The largest one has about 50,000 client records and it still works fine for speed but the users have already said they would like to see this change because now with 20+ years of client records, many are old or closed and so they would rather not see them anyhow so I had planned to filter this at some point to only show active clients). I could probably even implement this change before doing any SQL conversion and so they will see this as a new and improved feature to VFP instead of something to blame on SQL server.
>
>Regarding deleted records, they do indeed have a utility to restore deleted "quotes" for someone - occasionally someone deletes all the old quotes from someone in anticipation of closing the file. Would have to rework into it being a flag instead and by default filter them out. Good to know as that is going to involve some work.
>
>A new question: I take it that data could probably exist in both places as I go through the conversion (to a limited degree) - as long as the query is on a single table, it could be local or it could be on the server? correct? the only problem I would run into would be if the query was against more than one table.
>

Data should exists only in one place :-)
You take it, manipulate it and send it back to SQL Server.
The queries on SQL Server is the same as in VFP, you can query more than one table at a time, get one joined result set or get two or more result sets at a time.