>is very very long. Imagine that you have 30 fields. And this expression is created in a data driven approach scanning fields of the dictionary. Here is a segment of this code:
>
>

>cSqlInsert = "insert into " + ALLTRIM(DICT.TBL_NAME) + " "
>cSqlInsertValues = "" 
>
>DO WHILE !EOF() AND DICT.TBL_NAME = cTableName
>	
>   cSqlInsert = cSqlInsert + IIF( EMPTY(cSqlInsertValues),"( ",", ") + ALLTRIM(DICT.FLD_NAME) 
>		
>   cSqlInsertValues = cSqlInsertValues + IIF( EMPTY(cSqlInsertValues),"( ",", ") +  "?" + ALLTRIM(DICT.TBL_NAME) + "." + ALLTRIM(DICT.FLD_NAME) 
>	
>    SKIP IN DICT
>
>ENDDO 
>
>cSqlInsert = cSqlInsert + ") VALUES " + cSqlInsertValues + ")"
>

>
>So the above code creates this long cSqlInsert. Any suggestions on what to change?


That way of creating string variable can be longer that 256 chars :-)

What if:

cSqlInsert        = "insert into " + ALLTRIM(DICT.TBL_NAME) + "("
cSqlInsertValues = "" 
SCAN WHILE DICT.TBL_NAME = cTableName
     cSqlInsert       = cSqlInsert                                      +       ALLTRIM(DICT.FLD_NAME) + ", "
     cSqlInsertValues = cSqlInsertValues + "?" + ALLTRIM(DICT.TBL_NAME) + "." + ALLTRIM(DICT.FLD_NAME) +", " 
ENDSCAN
cSqlInsert = LEFT(cSqlInsert, LEN(cSqlInsert)-2)+ ") VALUES (" + LEFT(cSqlInsertValues, LEN(cSqlInsertValues)-2) + ")"

If you have problems, please write the cSqlInsert into text file and attach it here :-)