Login Form

#725 – Error on reports 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'FROM r202_bfsurvey_1results' at line 2 SQL=SELECT FROM r202_bfsurvey_1results

Posted in ‘BF Survey’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Monday, 05 October 2015 22:21 AEDT
David Henry
Joomla! version: 3.4.1

I'm getting the following error when testing the Reporting function.

1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'FROM r202_bfsurvey_1results' at line 2 SQL=SELECT FROM r202_bfsurvey_1results

I have tried maintenance > auto database cleanup but still get the error.

Any ideas?
Tuesday, 06 October 2015 12:26 AEDT
jeff
Google+ Authorlink 6 Months, BF User Log Plus 3 Years, BF Auction Plus 3 Years, BF Quiz Plus 3 Years, BF Survey 3 Years
Hi,

I would like to know where this is occuring. Is it on reports page? Adding a new report? Saving a report?
 
Tuesday, 06 October 2015 21:00 AEDT
David Henry
It happens after a report is created, if you try any of the export options it will be a problem

As this is a public question I can't send a user account, but you can find a user account to look into this on the previous ticket about a similar problem here:
http://tamlynsoftware.com/contact-us/support-tickets/bf-survey/712-unknown-column-researchandauditcpd-indic-in-where-clause-sql-select-from-r202-bfsurvey-1results-wher.html

David
Thursday, 08 October 2015 03:37 AEDT
jeff
Google+ Authorlink 6 Months, BF User Log Plus 3 Years, BF Auction Plus 3 Years, BF Quiz Plus 3 Years, BF Survey 3 Years
Hi David,

You forgot to add fields for the report.



I've added some fields, it should work now.

 
Wednesday, 11 November 2015 16:25 AEDT
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.
Go to top