Jason,

I haven't used the upsizing wizard in a while. I would certainly expect the SQL Server tables to look pretty much like the VFP tables. I don't remember what kind of stored procedures the wizard creates. As for whether you'll need to do more development it really depends on your application. If all the data access if through views and you had the upsizing wizard convert your local views to remote views you may be able to run the application as is. If you access the VFP tables directly you'll have to modify your code. No matter once, you'll probably have to do at least a little bit of tweaking.

>Hi Josh:
>
>I wrote you a quick note yesterday telling you that we figured out the best way to upsize our FoxPro 6.0 application to SQL Server. I ended up sending the application from my local computer to the person in our company who is basically the network administrator. He has SQL on his computer.
>
>Anway, the idea was for him to upsize the application I built on my computer to SQL Server on his computer. He was able to do that, however, he said that it didn't resemble anything like it was before the upsizing. He wants me to stop by his house to take a look at it tonight.
>
>My question is: Once our finished FoxPro application is upsized to SQL Server, is there a lot of new development that has to be done? Or, is it good to go? the way our network administrator was talking, it was a mess.... after he upsized. He said SQL Server created over 75 stored proceedures and the tables didn't look anything like what they had in FoxPro.
>
>I am just curious to know if you have done this, what type of work needs to be done after the upsizing to make it operate and look just like it did in FoxPro.
>
>If you have any thought or insight into this, I would sure appreciate any comments you might have.
>
>TIA
>Jason