Ed,
The reason I wrapped the execute with dDataSet was that I ran into a problem
issuing further execute statements on the result.
I'll have to track it down but if I recall this was the sitation...
myqueryresult = reportDS.execute('select * from dataset')
myqueryresult.execute('select * from dataset where whatever')
Would throw an exception saying myqueryresult was a list and had no execute
attribute or something like that.
Thanks for the input.
Larry
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Ed Leafe
> Sent: Tuesday, August 25, 2009 6:19 PM
> To: Dabo Users list
> Subject: Re: [dabo-users] Dataset question
>
> On Aug 25, 2009, at 5:41 PM, John wrote:
>
> > First the fix.
> > reportDS=dDataSet(reportDS.execute('select * from dataset'))
>
> This is redundant. The execute() method returns a
> dDataSet. No need to wrap it in yet another layer of dDataSet.
>
> > The issue appeared when a special requirement for the
> reports came up.
> > Larry wanted to retrieve data then delete a few of the
> records after
> > processing and that left a number of records that could be
> batched for
> > a second process.
> > The criteria for the retrieved data was the same for both processes
> > (so why make two calls). So he wanted to work with only
> one table.
> > It sounds very much like a VFP way of thinking where all that was
> > needed was a scan and process.
> >
> > It works and very well too.
>
>
> Maybe you guys are thinking of the filter() function of
> datasets?
>
>
> -- Ed Leafe
>
>
>
>
>
[excessive quoting removed by server]
_______________________________________________
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/!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAafA2fnYuPUOMNFpIYnBEQcKAAAAQAAAA8K8Fwe+OVEG/[email protected]
