Title: Problems Deleting ELI&#039;s SQL Admin Report
Last modified: August 20, 2016

---

# Problems Deleting ELI's SQL Admin Report

 *  Resolved [AlbertJPeters](https://wordpress.org/support/users/albertjpeters/)
 * (@albertjpeters)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/problems-deleting-elis-sql-admin-report/)
 * Eli’s SQL Reports Plugin is great – very helpful – but I think I created a monster!
   I constructed a report and named it “Deva’s Basic Listing”. Perhaps the apostrophe
   in the report name created issues, or maybe it’s something else, because any 
   time I try to delete the report (EDIT, then DELETE) I get ANOTHER report listing
   saved, with \ marks introduced into the title! This is what my dashboard displays
   now:
 * Deva\’s Basic Listing
    Deva\\\’s Basic Listing Deva\\\\\\\’s Basic Listing Deva\\\\\\\\\\\’
   s Basic Listing
 * …well, you get the idea. I tried uninstalling the plugin, deleting it, and reinstalling
   it. No effect. Can you help?
 * [http://wordpress.org/extend/plugins/elisqlreports/](http://wordpress.org/extend/plugins/elisqlreports/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Author [Eli](https://wordpress.org/support/users/scheeeli/)
 * (@scheeeli)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/problems-deleting-elis-sql-admin-report/#post-3533282)
 * I just uploaded version 1.3.03.02 that should fix this issue for you. After updating
   you should be able to delete those extra reports.
 * Please let me know if you need more help.
 * Aloha, Eli
 *  Thread Starter [AlbertJPeters](https://wordpress.org/support/users/albertjpeters/)
 * (@albertjpeters)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/problems-deleting-elis-sql-admin-report/#post-3533318)
 * eLI:
 * The update cured my can’t-delete-the-report problem, but now I’m getting the 
   following two notes at the top of the dashboard plugin window:
 * Warning: mysql_fetch_row() expects parameter 1 to be resource, boolean given 
   in /data/9/1/48/123/1700938/user/1835199/htdocs/bodyandsoltucsonroot/database1/
   wp-content/plugins/elisqlreports/index.php on line 158
 * Warning: mysql_free_result() expects parameter 1 to be resource, boolean given
   in /data/9/1/48/123/1700938/user/1835199/htdocs/bodyandsoltucsonroot/database1/
   wp-content/plugins/elisqlreports/index.php on line 161
    Saved /data/9/1/48/123/
   1700938/user/1835199/htdocs/bodyandsoltucsonroot/database1/wp-content/uploads/
   SQL_Backups/1_02c6d91_23.mysqlv103.2013-03-06-16-19-46.sql
 * Al Peters
 *  Plugin Author [Eli](https://wordpress.org/support/users/scheeeli/)
 * (@scheeeli)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/problems-deleting-elis-sql-admin-report/#post-3533330)
 * You got there error when using my new backup feature, right?
 * It would seem that there is a problem with the query I am using to determine 
   if you have any VIEWS to backup. I think this technique only works in the newest
   version of MySQL.
 * Anyway the backup feature is new and I am working on it now so you should see
   another release soon with that error fixed too.
 * Alloha, Eli

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Problems Deleting ELI's SQL Admin Report’ is closed to new replies.

 * ![](https://ps.w.org/elisqlreports/assets/icon-256x256.png?rev=1231385)
 * [EZ SQL Reports Shortcode Widget and DB Backup](https://wordpress.org/plugins/elisqlreports/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/elisqlreports/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/elisqlreports/)
 * [Active Topics](https://wordpress.org/support/plugin/elisqlreports/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/elisqlreports/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/elisqlreports/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Eli](https://wordpress.org/support/users/scheeeli/)
 * Last activity: [13 years, 2 months ago](https://wordpress.org/support/topic/problems-deleting-elis-sql-admin-report/#post-3533330)
 * Status: resolved