OutofMemory System expection when submitting to SQL

CCBSFranco — Tue, 10 Jun 2014 22:12:37 GMT

Hey everyone,

I have a InfoPath 2010 filler form injected with qdabra pulling about 750 rows from a SQL db. The end users make their changes to respective rows, in this case there's 100+ rows being manipulated then the user hits the submit button. Upon which they are greeted with a Out of Memory error.

The button has these rules and actions,

Delete the tables we are about to insert everything into.
Insert everything, all rows of data regarding user interface repeating table data, into one table for it's needed data
Insert one row for totals into the first table.
Delete all rows that were not manipulated in the user interface repeating table.
Then insert all rows that are left into the third table.
2 query transactions for 1 value each respectively and set that value to there respective needed field in the tables.
We then send all data into the SQL database tables. *disabled
Execute a Stored Procedure in SQL. *disabled
Show message that form submitted
Close

So far this has been a fine process until now. Could it be IP 2010 just cant handle that much data without a RAM increase? The current work station is windows 7 with 4gb RAM. The error takes about 30 minutes to present itself. What's even more bizarre rule 3 is the point at the error is reported, yet after hitting OK on the error box, the form remains unresponsive. After it comes back, bout 15-20mins later it has reached rule 9. I believe that it would have gone further and actually hit the system had rules 7 and 8 not been disabled, but this is a live system and I couldn't pump my test data into the system.

My user on the other hand says it never reached that point.

Any thoughts and questions are welcome.

General

OutofMemory System expection when submitting to SQL