Today I released the final version of SQLGridSelectedView V3.4e.  This is the non-beta release for the module. 

It seems I can't leave it alone. I had planned to just release this version with the one or two little issues corrected, but instead I had to add a bit more. 

Although I had not mentioned it, the beta's had some improved SQL error handling.  Previous versions would just dump the ASP.NET stack dump with all the detail including the SQL command being exeuted.  My original rational was I want to see where I screwed up as most of the SQL error were based on the program's attempts to build the SQL command.  Now that I seem to have that under control, I really didn't need to display all that extra stuff.  Also, I really didn't think about it until I got a comment from a user asking that I curb the detail displayed.  So, I have been cleaning up the error handling in V3.4

Two last pieces were required. The first, was an option to display the SQL command whenever a SQL error occured.  This was basically a way to keep the old functionality (less the ASP.NET procedureal stack dump).  The second piece was the addition of a comment stripper.  Several of the SQL errors I have encounter from user's E-mail were related to the inclusion of comments in the SQL command.  Either inline (/* ... */) and/or the -- to end of line type.  I have added these two pieces to SQLGridSelectedView.

The following are two examples of failed SQL commands. The second example demostrates the display of the SQL Command when the error occurs.  While you can't see it, the second module's SQL  Command contained comments there stripped.

Hope you find it useful.  Paul.