On Aug 8, 2007, at 11:45 AM, Mark Stanton wrote:
> I was wondering about an intermediate database, between the "app"
> and "appViews"
> databases that Codebook uses. The intermediate database would need
> one view
> for each codebook view and it would act like a "datalens" (TM 8-) )
> to restrict,
> or not, the main view.
The fields selected and their update status stays the same; it's
only the WHERE clause that changes. So binding to forms is no
problem, since the fields are the same.
The time I used the approach I outlined I defined the views to have
a WHERE clause of WHERE 1=0. When a bizobj was opened, it had a
reference to that primary view, which it would open NODATA and then
use CURSORGETPROP("SQL") to get the underlying SQL. When users
entered their criteria, I would form the WHERE clause dynamically,
substitute it for the "WHERE 1=0" of the original, and create an on-
the-fly view.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
