Changes in 1e45ff3: Updated Using Stored Procedures In Izenda 6 (markdown)

				FAQ/Questions/Using-Stored-Procedures-In-Izenda-6.md
			
          @@ -224,7 +224,7 @@ string currentReportName = HttpContext.Current.Request.QueryString["rn"];

           Since Izenda primarily uses metadata to obtain information about schemas, views, and other database objects, the same goes with stored procedures. Therefore, there are some expectations to be followed for these procedures that are to be used with Izenda.

          -Izenda sends NULL values for all parameters and expects to receive column headers with no data in return. This allows Izenda to create a temp table for the StoredProcedure to be reported on and joined like a view. 

          +Izenda sends NULL values for all parameters in a stored procedure and expects to receive column headers with no data in return. This allows Izenda to use the headers in the report designer just like a table or view to create reports. Additionally, at times Izenda needs to create a temp table from the StoredProcedure for joining to other tables and views, headers are used to create the temp table. 

           * INSERT EXEC - You cannot nest INSERT INTO ... EXEC statements in stored procedures used with Izenda. This is a limitation of SQL server.

           * Return columns - The stored procedure MUST return the same columns in all cases. It is because the metadata expected when running the stored procedure must comply with the specifications given to it.

...	...	@@ -224,7 +224,7 @@ string currentReportName = HttpContext.Current.Request.QueryString["rn"];
224	224
225	225	Since Izenda primarily uses metadata to obtain information about schemas, views, and other database objects, the same goes with stored procedures. Therefore, there are some expectations to be followed for these procedures that are to be used with Izenda.
226	226
227		-Izenda sends NULL values for all parameters and expects to receive column headers with no data in return. This allows Izenda to create a temp table for the StoredProcedure to be reported on and joined like a view.
	227	+Izenda sends NULL values for all parameters in a stored procedure and expects to receive column headers with no data in return. This allows Izenda to use the headers in the report designer just like a table or view to create reports. Additionally, at times Izenda needs to create a temp table from the StoredProcedure for joining to other tables and views, headers are used to create the temp table.
228	228
229	229	* INSERT EXEC - You cannot nest INSERT INTO ... EXEC statements in stored procedures used with Izenda. This is a limitation of SQL server.
230	230	* Return columns - The stored procedure MUST return the same columns in all cases. It is because the metadata expected when running the stored procedure must comply with the specifications given to it.