>>
>>This has been forcing me to use standard SQL Cursors for my reporting, which I don't mind, but I'd like to keep to the framework ideals. Does anyone have a suggestion? The data in view1 is usually the Id of it's underlying table.
>>
>
> I tend to use SQL code in my reports and bypass the views. SQL code for reports tend to be a lot more hairy than what I'll use in my views and I like to avoid the types problems you're seeing. I normally do this knowing full well if I switch backends that I will need to switch over to SPT or stored procedures. I think it's a reasonable trade-off.
>
> However, with the latest version of the framework you can wrap these in a SQL pass through connection and hit local data instead of SQL server. I'm not entirely sure if it's possible to do this w/o ODBC or (under VFP 7) OLE-DB. If not, maybe there should be. I haven't had an opportunity to try this, so YMMV.

Paul,
I'm beginning to think you're right here. The trade-off was what I was trying to avoid.
And I'm not familiar with YMMV.