note 110234 added to function.mssql-execute

Interesting little quirk I noticed: You can't initialize, execute, and free stored procedures in a nested fashion. e.g this pattern: <?php $statement1 = mssql_init('statement1'); //some binds and stuff $statement2 = mssql_init('statement2'); //some binds and stuff mssql_execute($statement2); mssql_free_statement($statement2); mssql_execute($statement1); ?> will fail when you execute statement 2. Not only will it fail, but you won't get any results back from mssql_get_last_message(), so it's super-frustrating. The way around this is to rearrange the structure of your script so that stored procedures are executed sequentially. ---- Server IP: 69.147.83.199 Probable Submitter: 69.176.119.146 ---- Manual Page -- http://www.php.net/manual/en/function.mssql-execute.php Edit -- https://master.php.net/note/edit/110234 Del: integrated -- https://master.php.net/note/delete/110234/integrated Del: useless -- https://master.php.net/note/delete/110234/useless Del: bad code -- https://master.php.net/note/delete/110234/bad+code Del: spam -- https://master.php.net/note/delete/110234/spam Del: non-english -- https://master.php.net/note/delete/110234/non-english Del: in docs -- https://master.php.net/note/delete/110234/in+docs Del: other reasons-- https://master.php.net/note/delete/110234 Reject -- https://master.php.net/note/reject/110234 Search -- https://master.php.net/manage/user-notes.php