>>This doesn't sound like a good thing to me: it would require two different languages within a project, it would be slower, and it wouldn't work off cursors.
>
>I'm with Garrett, antoher reason is now that VFP is on its own, it should create a preception that its an all in one, ready to go Database language. If we're going to downplay the VFP cursor as much as possible, why even sell VFP?


You'd only be losing the cursor support. You'd still be able to access VFP tables and views via ODBC or ADO and Fox2X tables natively. Doing:

SELECT MyCursor
COPY TO MyTable TYPE FOX2X

then running the Crystal report is not that big of a deal.