I am sure they added a lot of features to the latest version of SFQUERY. I should probably look at the demo but no time for that now. I will just have to use the current version I have, for now.

Thank you for your input.

>They have 2 pricing models, both of which are more expensive than what you currently have.
>Model 1 - pay per seat.
>Model 2 - you pay a flat fee for an unlimited run-time license. That means you can develop reports and distribute them to your clients. The client can run the report, setting selection criteria and sort sequences at run-time, but they cannot define new report formats.
>
>I know that this sucks, I was very disappointed when I found out about it, but there is still a lot of value there.
>
>>Thank you for your suggestion. But, from what I know, I am not sure I want to buy the latest version of SF Query. I think now they charge for each license use (e.g. customer) whereas the version I have I can incorporate into my application and provide it to each of my customers, without paying the fee.
>>
>>
>>>The latest versions of SF Query have full support for SQL Server.
>>>Unfortunately I do not know the details, as I do not use SQL myself,
>>>but I suggest you contact them directly.
>>>
>>>>In my VFP applications I am using SFQUERY to create filters/queries for user-defined reports. I would like to continue using SFQUERY when creating reports based on the data in SQL Server. At the first glance, the way I see it, I would have to have a "dummy" VFP database and tables to match the tables and fields of the SQL Server. Then I would create a query string based on the VFP database and tables and then use it on SQL Server.
>>>>
>>>>Does the above approach seem like a logical and practical method?
>>>>
>>>>Does anybody use SFQUERY with SQL Server?
>>>>
>>>>I use the older version of SFQUERY (v 6, that was in beta but was never released).
>>>>
>>>>Thank you in advance for any suggestions.