No Bloody messages here from me...

I assume that your system you are converting is a VFP app, and you want to scale it to SQL server ? If that is the case... then depending on how the code was written, using views and other factors you could acheive very very good results using VFP as the client to a client server application with MsSql as the back end, keeping the reports as is, running VFP for the data entry screens, and reports..

I am not saying this is easy... as nothing is going to be easy or quick when you take a large application and convert it to a new database.. before you toss out the baby with the bathwater, I truly suggest that you look into VFP's client Server capilities. Actually IMO They work great.

Bob Lee


>Good Day:
> I hope I don't get too bloody by posting this message here, but here we go. My company has a rather large internal system built by a single developer that I am trying to Migrate to SQL Server. In the experience of this venerable group, what is the best way(Off the shelf program? VB? Access? What?) to provide users with the Forms and Reports functionality from VFP?
>
>Thank You,
>Omar Soto