There is no reason to have different reports for VFP than for SQL Server...and you can just use the VFP Report Designer, which doesn't have all the bells and whistles of Crystal Reports, but is easier to use.

Base your report data on a View. Name the view the same for a remote view as a local view, then just change the view property to make it local or remote.



>Thank you.
>The thing is that we are porting our application to work with both SQL Server and VFP back end, maybe later add MySQL. Originally all our reports were written using VFP report writer, but with multiple backend I thought that Crystal Report will work better and will be easier to maintain; create one report and change connections depends on the back end. Or so I thought.... Now, I can see that while SQL ODBC allows me to work with SQL Views and Stored Procedures seamlessly, this is not so easy for VFP. So I cannot create stored procedure in both to get the same result and build report based on it.
>Oh well, will try a different approach or create a second set of reports in VFP
>Thank you again