🚀 go-pugleaf

Nicolas GASNIER wrote:
> Hi,
> 
> I want to improve my user interface reactivity by setting the 
> Load.ASYNCHRONOUS option on my QueryDataSet. On this dataset, I have a 
> "navigated" event I use to refresh two other datasets based on the the 
> current row ID (I don't want to use mastelinks, the detail dataset would be 
> too big). But this sometimes causes deadlocks between the event thread and 
> the thread of the provider. I think the first dataset I'm trying to refresh 
> wait for the QueryProvider to be released by the main dataset, but for a 
> reason I don't really understand, the main dataset is waiting for that too.
> 
> Does anyone experienced such problem, and how did you manage to solve it ?

I have not experienced this problem, nor do I remember anyone reporting 
it here..

Some questions:

1) You imply that both the detail and master datasets are using the 
"same" instance of QueryProvider.  Is that correct?

2) If so I would question the wisdom of this..  (DX if left to it's 
defaults creates a new instance of the default QueryProvider for each 
instance of QueryDataSet. (example out of DX QueryDataSet source**)

if (currentProvider == null) {
       setQueryProvider(new QueryProvider());
       currentProvider.setAccumulateResults(accumulateResults);
}

..where..

private void setQueryProvider(QueryProvider provider) /*-throws 
DataSetException-*/ {
     super.setProvider(provider);
     currentProvider = (QueryProvider)provider;
}

So.. I would guess you could be doing something else that is forcing the 
QueryDataSet to share a Provider.. (Maybe you should not be doing that..??)

Hope that helps..

John..




-- 
=============================================
TeamB are volunteer helpers.  Please DO NOT REPLY VIA EMAIL!
Post all questions and replies to this newsgroup ONLY
For papers on DataExpress, Applets, JSP, and Web Development go to:
http://www.microps.com/mps/paperFAQ.html
====================================================