QueryAdtapter Timeout value

D

Dde

I put the code in the form onload event to set a webservice adapter timeout
to 120 sec the following way:

XDocument.DataObjects("EstimateOptim").QueryAdapter.Timeout = 120;

In my form I call this query by a rule but it still times out after 30 sec.
I treied to display the timeout value with a UI.Alert and it displays 120!

Thanks
Dominique
 
D

Dde

This datasource is NOT loaded by default, but still the timeout remains 30
sec.
Dominique

"Greg Collins [InfoPath MVP]" <Greg.Collins_AT_InfoPathDev.com> wrote in
message Secondary data sources are loaded before the OnLoad event handler is
processed. This is because things like User Roles might point to a data
source--so that information has to be there early on.

You will need to tell your secondary data source to NOT load by default...
Then in your OnLoad handler you can set the timeout and then manually query.

This should solve your issue.
 
D

Dde

Will give that a try tomorow.
Thanks

"Greg Collins [InfoPath MVP]" <Greg.Collins_AT_InfoPathDev.com> wrote in
message Perhaps there is something about calling Query from rules that sets that
timeout back to the default value.

Try creating a second query button (or whatever you are using) which calls
into code instead of using a rule. Have your code physically set the timout
and then do a query. See if that makes a difference.

Hey Microsoft, if your listening -- is there something about rules that sets
the timeout back to the default value?

--
Greg Collins [InfoPath MVP]
Please visit: http://www.InfoPathDev.com



This datasource is NOT loaded by default, but still the timeout remains 30
sec.
Dominique

"Greg Collins [InfoPath MVP]" <Greg.Collins_AT_InfoPathDev.com> wrote in
message Secondary data sources are loaded before the OnLoad event handler is
processed. This is because things like User Roles might point to a data
source--so that information has to be there early on.

You will need to tell your secondary data source to NOT load by default...
Then in your OnLoad handler you can set the timeout and then manually query.

This should solve your issue.
 
J

jb

I set *all* my timeouts high (for debugging in MSE), and I use code (not
rules) for all filling, and it works OK for me.
 
D

Dde

Does it mean you can use NO rules at all ?

Thanks,
Dominique

jb said:
I set *all* my timeouts high (for debugging in MSE), and I use code (not
rules) for all filling, and it works OK for me.

Dde said:
Will give that a try tomorow.
Thanks

"Greg Collins [InfoPath MVP]" <Greg.Collins_AT_InfoPathDev.com> wrote in
message Perhaps there is something about calling Query from rules that sets that
timeout back to the default value.

Try creating a second query button (or whatever you are using) which calls
into code instead of using a rule. Have your code physically set the timout
and then do a query. See if that makes a difference.

Hey Microsoft, if your listening -- is there something about rules that sets
the timeout back to the default value?

--
Greg Collins [InfoPath MVP]
Please visit: http://www.InfoPathDev.com



This datasource is NOT loaded by default, but still the timeout remains 30
sec.
Dominique

"Greg Collins [InfoPath MVP]" <Greg.Collins_AT_InfoPathDev.com> wrote in
message Secondary data sources are loaded before the OnLoad event handler is
processed. This is because things like User Roles might point to a data
source--so that information has to be there early on.

You will need to tell your secondary data source to NOT load by default...
Then in your OnLoad handler you can set the timeout and then manually query.

This should solve your issue.
Click to expand...
Click to expand...
 
D

Dde

Hi,

Tried his soluion but it doesn't work either .....
Dominique

"Greg Collins [InfoPath MVP]" <Greg.Collins_AT_InfoPathDev.com> wrote in
message Perhaps there is something about calling Query from rules that sets that
timeout back to the default value.

Try creating a second query button (or whatever you are using) which calls
into code instead of using a rule. Have your code physically set the timout
and then do a query. See if that makes a difference.

Hey Microsoft, if your listening -- is there something about rules that sets
the timeout back to the default value?

--
Greg Collins [InfoPath MVP]
Please visit: http://www.InfoPathDev.com



This datasource is NOT loaded by default, but still the timeout remains 30
sec.
Dominique

"Greg Collins [InfoPath MVP]" <Greg.Collins_AT_InfoPathDev.com> wrote in
message Secondary data sources are loaded before the OnLoad event handler is
processed. This is because things like User Roles might point to a data
source--so that information has to be there early on.

You will need to tell your secondary data source to NOT load by default...
Then in your OnLoad handler you can set the timeout and then manually query.

This should solve your issue.
 
J

jb

I'm not using any rules anywhere. I haven't tested whether rules would make
anything not work. I can only say the timeout does seem to work for me,
using code. BTW, I use a WebService QueryAdapter --- no guarantee there
might be a difference for timeouts on different types of adapter.

Dde said:
Does it mean you can use NO rules at all ?

Thanks,
Dominique

jb said:
I set *all* my timeouts high (for debugging in MSE), and I use code (not
rules) for all filling, and it works OK for me.

Dde said:
Will give that a try tomorow.
Thanks

"Greg Collins [InfoPath MVP]" <Greg.Collins_AT_InfoPathDev.com> wrote in
message Perhaps there is something about calling Query from rules that sets that
timeout back to the default value.

Try creating a second query button (or whatever you are using) which calls
into code instead of using a rule. Have your code physically set the timout
and then do a query. See if that makes a difference.

Hey Microsoft, if your listening -- is there something about rules that sets
the timeout back to the default value?

--
Greg Collins [InfoPath MVP]
Please visit: http://www.InfoPathDev.com



This datasource is NOT loaded by default, but still the timeout remains 30
sec.
Dominique

"Greg Collins [InfoPath MVP]" <Greg.Collins_AT_InfoPathDev.com> wrote in
message Secondary data sources are loaded before the OnLoad event handler is
processed. This is because things like User Roles might point to a data
source--so that information has to be there early on.

You will need to tell your secondary data source to NOT load by default...
Then in your OnLoad handler you can set the timeout and then manually query.

This should solve your issue.
Click to expand...
Click to expand...
Click to expand...
 
D

Dde

Hi,

I use this code on a button vor mty Web Service query adapter:

function CTRL380_6::OnClick(eventObj) {
// Write your code here
XDocument.UI.Alert("This operation can take up to one minute.");
XDocument.DataObjects("EstimateOptim").QueryAdapter.Timeout = 120;
XDocument.DataObjects("EstimateOptim").QueryAdapter.Query();
}

but I also have some rules on other objects. Whatever I do, the WS adapter
still times out after 30 sec.
Dominique

jb said:
I'm not using any rules anywhere. I haven't tested whether rules would make
anything not work. I can only say the timeout does seem to work for me,
using code. BTW, I use a WebService QueryAdapter --- no guarantee there
might be a difference for timeouts on different types of adapter.

Dde said:
Does it mean you can use NO rules at all ?

Thanks,
Dominique

jb said:
I set *all* my timeouts high (for debugging in MSE), and I use code (not
rules) for all filling, and it works OK for me.

:

Will give that a try tomorow.
Thanks

"Greg Collins [InfoPath MVP]" <Greg.Collins_AT_InfoPathDev.com> wrote in
message Perhaps there is something about calling Query from rules that sets that
timeout back to the default value.

Try creating a second query button (or whatever you are using) which calls
into code instead of using a rule. Have your code physically set the timout
and then do a query. See if that makes a difference.

Hey Microsoft, if your listening -- is there something about rules
Click to expand...
that
sets
the timeout back to the default value?

--
Greg Collins [InfoPath MVP]
Please visit: http://www.InfoPathDev.com



This datasource is NOT loaded by default, but still the timeout
Click to expand...
remains
30
sec.
Dominique

"Greg Collins [InfoPath MVP]" <Greg.Collins_AT_InfoPathDev.com> wrote in
message Secondary data sources are loaded before the OnLoad event handler is
processed. This is because things like User Roles might point to a data
source--so that information has to be there early on.

You will need to tell your secondary data source to NOT load by default...
Then in your OnLoad handler you can set the timeout and then
Click to expand...
manually
query.
This should solve your issue.
Click to expand...
Click to expand...
Click to expand...
 
J

jb

Sorry, can't help any more. You've done the right thing and all you can, I
think...

Dde said:
Hi,

I use this code on a button vor mty Web Service query adapter:

function CTRL380_6::OnClick(eventObj) {
// Write your code here
XDocument.UI.Alert("This operation can take up to one minute.");
XDocument.DataObjects("EstimateOptim").QueryAdapter.Timeout = 120;
XDocument.DataObjects("EstimateOptim").QueryAdapter.Query();
}

but I also have some rules on other objects. Whatever I do, the WS adapter
still times out after 30 sec.
Dominique

jb said:
I'm not using any rules anywhere. I haven't tested whether rules would make
anything not work. I can only say the timeout does seem to work for me,
using code. BTW, I use a WebService QueryAdapter --- no guarantee there
might be a difference for timeouts on different types of adapter.

Dde said:
Does it mean you can use NO rules at all ?

Thanks,
Dominique

I set *all* my timeouts high (for debugging in MSE), and I use code (not
rules) for all filling, and it works OK for me.

:

Will give that a try tomorow.
Thanks

"Greg Collins [InfoPath MVP]" <Greg.Collins_AT_InfoPathDev.com> wrote in
message Perhaps there is something about calling Query from rules that sets that
timeout back to the default value.

Try creating a second query button (or whatever you are using) which
calls
into code instead of using a rule. Have your code physically set the
timout
and then do a query. See if that makes a difference.

Hey Microsoft, if your listening -- is there something about rules that
sets
the timeout back to the default value?

--
Greg Collins [InfoPath MVP]
Please visit: http://www.InfoPathDev.com



This datasource is NOT loaded by default, but still the timeout remains
30
sec.
Dominique

"Greg Collins [InfoPath MVP]" <Greg.Collins_AT_InfoPathDev.com> wrote in
message Secondary data sources are loaded before the OnLoad event handler is
processed. This is because things like User Roles might point to a data
source--so that information has to be there early on.

You will need to tell your secondary data source to NOT load by
default...
Then in your OnLoad handler you can set the timeout and then manually
query.

This should solve your issue.
Click to expand...
Click to expand...
Click to expand...
 
J

jb

Sorry, can't help any more. You've done the right thing and all you can, I
think...

Dde said:
Hi,

I use this code on a button vor mty Web Service query adapter:

function CTRL380_6::OnClick(eventObj) {
// Write your code here
XDocument.UI.Alert("This operation can take up to one minute.");
XDocument.DataObjects("EstimateOptim").QueryAdapter.Timeout = 120;
XDocument.DataObjects("EstimateOptim").QueryAdapter.Query();
}

but I also have some rules on other objects. Whatever I do, the WS adapter
still times out after 30 sec.
Dominique

jb said:
I'm not using any rules anywhere. I haven't tested whether rules would make
anything not work. I can only say the timeout does seem to work for me,
using code. BTW, I use a WebService QueryAdapter --- no guarantee there
might be a difference for timeouts on different types of adapter.

Dde said:
Does it mean you can use NO rules at all ?

Thanks,
Dominique

I set *all* my timeouts high (for debugging in MSE), and I use code (not
rules) for all filling, and it works OK for me.

:

Will give that a try tomorow.
Thanks

"Greg Collins [InfoPath MVP]" <Greg.Collins_AT_InfoPathDev.com> wrote in
message Perhaps there is something about calling Query from rules that sets that
timeout back to the default value.

Try creating a second query button (or whatever you are using) which
calls
into code instead of using a rule. Have your code physically set the
timout
and then do a query. See if that makes a difference.

Hey Microsoft, if your listening -- is there something about rules that
sets
the timeout back to the default value?

--
Greg Collins [InfoPath MVP]
Please visit: http://www.InfoPathDev.com



This datasource is NOT loaded by default, but still the timeout remains
30
sec.
Dominique

"Greg Collins [InfoPath MVP]" <Greg.Collins_AT_InfoPathDev.com> wrote in
message Secondary data sources are loaded before the OnLoad event handler is
processed. This is because things like User Roles might point to a data
source--so that information has to be there early on.

You will need to tell your secondary data source to NOT load by
default...
Then in your OnLoad handler you can set the timeout and then manually
query.

This should solve your issue.
Click to expand...
Click to expand...
Click to expand...
 
Top