This forum is no longer open and is for reading/searching only.
Please use our new MachForm Community Forum instead.
MachForm Community Forums » MachForm 3
Entries Tab
Started 12 years ago by clbks | 6 posts |
-
With one of my forms when I click on the Entries Tab to view submissions I get the following error. All other forms work fine.
SQL: [672] select A.element_id, A.option_id, (select if(B.element_matrix_parent_id=0,A.option, (select C.
option
from ap_element_options C where C.element_id=B.element_matrix_parent_id and C.form_id=A.form_id and C.live=1 and C.option_id=A.option_id)) ) 'option_label' from ap_element_options A left join ap_form_elements B on (A.element_id=B.element_id and A Params: 1 Key: Position #0: paramno=0 name=[0] "" is_param=1 param_type=2 Query Failed: SQLSTATE[21000]: Cardinality violation: 1242 Subquery returns more than 1 rowPosted 12 years ago # -
Hi,
It seems you have problem with one of your form entry and we need to check the problem further.
Could you send your ftp and machform login info to :customer.service[at]appnitro.com
MachForm Support
Posted 12 years ago # -
I have about half of my forms giving this error. (V3.2) No rhyme or reason... I would give you my FTP but I upload directly to my host... can i just get you my login and password?
Posted 12 years ago # -
First off, can't praise you guys enough, this is a really fantastic application, keep up your great work!
I have this problem too and it appear to happen as soon as you have 10 or more forms. If you call /manage_entries.php?id=10 with a double digit number the SQLerror above is displayed and you cannot see any entries. I am just going to investigate the code as it's preventing me from getting at data for one of my critical forms.
Hope this helps and will re-post if I find the problem!
Posted 12 years ago # -
If you haven't updated to v3.3, I suggest to update your machform. There was some bug with the previous versions that occured on certain conditions and caused errors as above.
MachForm Founder
Posted 12 years ago # -
I upgraded to v3.3 over the weekend but the problem is exactly the same? I have taken a quick look but do not have much time at the moment and was unable to find the problem? Your help would be appreciated.
Posted 12 years ago #
Reply
You must log in to post.