On Saturday 28 February 2009 06:32:27 am Ed Leafe wrote: > My actual SQL Selects are complex and I prefer to do UserSQL rather > than the alternative line-by-line specification if at all possible.
I have some fairly complex bizObj's that are created using the standard Dabo "setWhere" and "setJoin". The advantage is small if any. But I thought if I ever change the backend database of my project that Dabo would handle the change better than me defining UserSQL. Of course this could just my imagination. Blowing my own theory I use tempCursors a lot. I create them by hand edited SQL statements. There are two reason I need them. 1. I have a dataset and need to filter, or retrieve special relations from the dataset. 2. I have the "USE AGAIN" requirement. Which is a need to access the same table twice with different views. Of course the in the second case I could just create a "View". -- John Fabiani _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
