>Kevin,
>
>I have a situation where the view designer just isn't flexible enough for what I want to do, so I have decided to use SQL pass through to accomplish it. I am wondering if you could give me any insight on how to use SQL pass through with the framework, specifically kBizObj?
>
>Thanks,
>Doug Stalter
>Mammography Reporting System


If you use SQL Passthrough the cursor returned is going to be read-only and any updates are going to require more SQL Passthrough. If this is the case, then a business object becomes unnecessary.

If you want to use a business object for things like navigation etc. you could create a subclass of the kBizObj and store the passthrough statement, cursor name etc and have code in the requery that executes the call.

Using a view would be simpler. You can create the view in code. I have some that cause the view designer to abort if I try to load them but I did use the view designer to get the basics of the view and then finished it in code (it's handy to do that so the SQLSETPROP etc statements are available. I use gendbc to get the view info into a program.)