SC BUGS - Fix Macro

[Frogie]

OMG - this is so crazy. I can’t imagine how someone who creates Help files can put up something like this. This absolutely makes no sense and is as confusing as it gets!
This really is not Enaglish that a normal human being can understand (unless it is a Netmake Help editor person). P{UR GARBAGE !!!

PLEASE FIX YOUR MACRO HELP - THIS IS THE MOST IMPORTAN PART OF DOCUMENTATION !!!

[ATTACH=JSON]{“data-align”:“none”,“data-size”:“full”,“title”:“2018-12-11 22_13_20-Macros - Scriptcase Manual.jpg”,“data-attachmentid”:85692}[/ATTACH]

[Frogie]

I’m trying to use sc macro and I get ewrrors, so either there is a bug or I completely do not understand how this macro should be applied.
I noticed that when the column reference is given in the form of TableName.ColumnName often Sc goes crazy and throws Errors. Not sure if this is a case, but obviously seeing HELP descriptions like the one above makes me very, very mad !

Here is the code I used:

$sql = "UPDATE ins_customers SET ins_customers.Selected = 1";

$save_current_where = {sc_where_current};
if($save_current_where !=""){
    $sql .= " $save_current_where";     
}

sc_exec_sql($sql);

echo "All records selected: $save_current_where";

so the App comlains about the non existing field (while the field exsitst).

here is the error :

[ATTACH=JSON]{“data-align”:“none”,“data-size”:“full”,“title”:“2018-12-11 22_24_15-main_menu.jpg”,“data-attachmentid”:85694}[/ATTACH]

[ctmservice]

I think there is a fault in your sql-syntax and/or database-table. The best is to test the sql outside SC (I use Navicat, but any other will do) and so see where its wrong. Aftter correcting you can paste it back in SC.

[tfertil]

Hi Frogie. About this:

“so the App comlains about the non existing field (while the field exsitst).”

Maybe the field exists, but it’s prefixed with a different table name that the one in the update sentence. It’s on a different table? Your SELECT sentence includes a JOIN? Then your update sentence must include a JOIN too.

Regards,

[Eduardo_Kahn]

Hello Frogie,

About the first problem, I sent it to the person in charge of this to replace the text with another better text.

About the second problem, I talked to you through the email.

[Frogie]

Thank you all. I have the Error problem sort out. The crappy MACRO help problem remains.
This is the most important part of the documentations for SC and it really, really sucks. We keep asking for years to get somebody to do proofreading for the Help file and everything is ignored.

Eduardo Kahn
Bug Tracker Team ----------- WHEN YOU FINALLY FIX THOSE ISSUES. The English in the help is mess and you need to get someone who speaks/writes fluent English. There is ton of places where your help makes no sense ! Over the years I’ve learned from other users how certain things work, but if new user wants to realy on your help (and no ecternal help from other users) SC product help pages simply suck - PERIOD