Long query time... disable Infopath warning

[morten w]

Dear InfoPath community,
A MSDN technical article on Infopath2007 says:
InfoPath 2007 has added several features to help improve the experience with
data connections:
The UI enables the end user to cancel the query if it is taking too long to
execute.
The message is:

"The query returned large amounts of data and rendering your form may take
some time.
Do you want to continue?" (Yes / No)

My question is: How do you disable this message? Can I?

I have developed a "pure SQL 2005" form that runs some "complex" SQL queries
using drop-down list boxes. Every time I change a value in a drop down box, I
get that InfoPath "warning"...imagine that 10 users have to click yes 100
times a day...

All help will be appreciated.

 

[Mooky]

The worst part is, the infopath forms services site the form gets posted on,
doesnt even give detailed information. something like "There has been an
error while processing the form". It took me a second to put the two
together. I get the error when i hit submit query from the template that says
large amounts of data etc. I am experiencing the same thing and its quite
ridiculous that they didnt experience this behavior in any testing. Im simply
connecting to a DB/Table on the LAN, trying to retrieve simple data in hopes
of doing some more advanced stuff with the business catalog etc. and cant
even scale right off the bat. Im assuming i have to write some custom code to
suppress that message. That means that ill have custom code and have to do
the whole administrator approved template thing.

Does anyone have any better ideas???

 

[morten w]

And i only have 160 records.....what do you mean by the whole administrator
approved template thing?

 

[Mooky]

I believe you can add custom code to the run query button (or change it to a
custom code/rules button) that will suppress the error message. However, once
you do that, you dont get the option to just simply post to a doc library,
create one on the fly etc. You must select "administrator approved template",
copy the template to the local (i think the local part is optional)
sharepoint server then go into the central admin site, upload the template
through that, etc. Quite more complex than saying "publish to a sharepoint
site" and "ok". I understand the security implications with allowing joe user
to post a form template that runs code on a web server but there has to be a
better way than the junk i currently have to go through.

Pretty weak IMO.