InfoPath Dev

 We have a secondary connection that is dynamically set using code behind and if the number or records is large, over say 100 or so, the buttons on the default view don't work. We can use the client's dropdown to change view but the buttons just show a spinning cursor when clicked. The button is set to switch views on button click. Smaller views and the xml files don't pose a problem and everything works fine.

The code behind uses a dropdown to determine which view in a large list to use and sets the xml connection string accordingly. Everything works well except the buttons for navigation. When change the secondary connection to a SharePoint library and pull the entire list the navigation works. However the list has over 5000 records and we have a problem the view threshold limits.

I used the following blog as a starting point for the code: http://www.bizsupportonline.net/browserforms/dynamically-fill-drop-down-list-box-browser-form-using-other-form-as-source.htm

So the question is would the size of the view and the associated xml be limited by a size or number of characters with would bleed over and stop the buttons from working?

Hi - is this a filler or browser form? What happens if you just wait it out - does the view finally switch? Would the view you are switching to be quite long due to the amount of records and thus take a long time to navigate? Have you tried running your code in debug to see if it is the code execution that is causing the delay?

 Filler form, the cursor spins and then does nothing and the view doesn't change. We can quickly change view in the client by clicking on the Home tab and changing views. This code works for 60 different views just not the ones with larger record sets. I have trimmed the record set by adding additional filters which slowly reduce the number of records and once it is small enough the buttons work. the code is short and clean and it would fail on smaller views if it were the code: I believe.

I have looked at the responses in Fiddler but I don't see anything that stands out besides the size of the data pulled in with the view/xml.

About how many rows of data do you pull back where you find the view switch is working? I've not run into this before - I have had views with a ton of repeating data displayed that might be very slow to switch, but never that it absolutely kills InfoPath.

 I will have to repeat the test to give you the number at which it fails. Somewhere around 100 or so. Note: everything in the form works including the sections that consumes the data in the form. Only the buttons that act as navigation on the default page, but unfortunately, the users have trouble using the client's navigation : Home => Current View selector.

I will see if I can't pin point the number and post that.

Well, and is the view you are switching to the view you are displaying these items in?

You could, just for testing, add controls to the view your button is in to display the data - and not switch views. Does the form hang then? I mean, it will for a while it renders the repeating data, but you could at least see if you have the same behavior.

 To follow up on my testing, I have been deleting by groups of 10 in the view and 131 records failed, 121 records worked.

Nothing else was changed in the form just the number of records retrieved by the list view.