 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWordDirectoryUser Groups Related Topics Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ... |
MS Office Forum / General MS InfoPath Questions / December 2004QueryAdtapter Timeout value
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 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.  SignatureGreg Collins [InfoPath MVP] Please visit: http://www.InfoPathDev.com 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 This datasource is NOT loaded by default, but still the timeout remains 30 sec. Dominique 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. SignatureGreg Collins [InfoPath MVP] Please visit: http://www.InfoPathDev.com 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? SignatureGreg 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 news:OhbuU2U4EHA.3388@TK2MSFTNGP15.phx.gbl... 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. SignatureGreg Collins [InfoPath MVP] Please visit: http://www.InfoPathDev.com Will give that a try tomorow. Thanks 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? SignatureGreg 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 news:OhbuU2U4EHA.3388@TK2MSFTNGP15.phx.gbl... 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. SignatureGreg Collins [InfoPath MVP] Please visit: http://www.InfoPathDev.com 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 [quoted text clipped - 23 lines] > > This should solve your issue. 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. [quoted text clipped - 26 lines] > > > > This should solve your issue. 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. > Does it mean you can use NO rules at all ? > [quoted text clipped - 37 lines] > > > > > > This should solve your issue. 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 > 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, [quoted text clipped - 42 lines] > > > > > > > > This should solve your issue. Sorry, can't help any more. You've done the right thing and all you can, I think... > Hi, > [quoted text clipped - 68 lines] > > > > > > > > > > This should solve your issue. Sorry, can't help any more. You've done the right thing and all you can, I think... > Hi, > [quoted text clipped - 68 lines] > > > > > > > > > > This should solve your issue. Ok fine, thanks anyway. Dominique Hi, Tried his soluion but it doesn't work either ..... Dominique 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? SignatureGreg 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 news:OhbuU2U4EHA.3388@TK2MSFTNGP15.phx.gbl... 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. SignatureGreg Collins [InfoPath MVP] Please visit: http://www.InfoPathDev.com
|
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.