Constant SQL errors on form in V9

Scriptcase 9 General
#1

I was wondering if anyone is having the problems I am with forms. I have created single record forms and added Master/Detail forms (where the detail forms are multiple records). When testing the application, it forces me to enter the parameter to satisfy the primary key, as expected. Whenever I try to fiddle with the layout of the detail forms, specifically placing them in new pages (for showing them in tabs) I now get SQL errors. This one just happened to me:

Error while accessing the database
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 ‘as sc_field_0, as sc_field_1 from parcel_owner WHERE (po_cad_id = ‘148252’’ at line 1

Then when I go back and reverse what I changed, and save the application again, the SQL error persists. I can never come back from it. It shouldn’t be this complicated to embed some details in a form. This tool is getting very frustrating for me despite reading the documentation (which is rather weak and not very intuitive). Any ideas are appreciated.

#2

Not exactly what you described, but
I noticed that one has to configure the whole application again if the SQL statement was changed only a bit.
Especially in connection with Scriptcase’s GROUP BY features.

If existing fields did not change by editing the SQL, this behaviour shouldn’t happen. Very bad user experience.
I believe it’s a common use case to add another field via SQL without changing the whole application.

#3

I think there is something wrong in your SQL syntax. I always copy (or rebuild) the SQL in that cases outside scriptcase (I use Navicat, but phpadmin will also do).
Or you use the SQL-builder in SC. But better is outside.
When there are globals you have to replace them with real characters or numbers. Then you see soon if the syntax is ok or not and you know if it has something to do with SC.

#4

Already checked that. I always build my queries outside of SC before even trying to use them in a grid. There’s just no reason for SC to reset all of your fields in your applications if edits are made to the SQL query field. It does it constantly.

#5

I got the same now. Make a query outside SC where it runs fine and then put it in a grid of SC and it gives errors…strange.