It does sound like we're doing pretty much the same thing. I also remove any UPPER() functions because SQL Server doesn't support upper and it's not really necessary if you have it set to not use case-sensitive data.

If a field doesn't accept nulls you'll need to supply some kind of values. This could be with a default in the server or by defaulting the value in the front end when the user adds a record. You could also just set the field to allow nulls is that's apprpriate.

>Hi Josh,
>I am in the process of converting my VFP app to also run SQL Server. It looks like I have a simular strategy. Glad to hear I'm not alone!<g> The function I wrote to handle SPT handles quotes ok and I've just discovered I need to convert .T. and .F. Any other gotchas you're willing to share?
>
>Also, when I tried to add a record for the first time via a Remote View, I got an error that a field doesn't accept NULLs. Do I need to have Defaults set up on all the fields in the view? Or am I missing something else?
>
>TIA,
>Bill