PowerScript embedded SQL doesn't like reserved words used as identifiers. Same goes for DataWindow SQL syntax.

However, it IS possible - in both instances - this way:

1. Ensure your DB connection uses DelimitIdentifier=1
2. CONSEQUENCE => All strings in embedded SQL and in DataWindow SQL MUST use single quotes.
3. Surround every identifier = "reserved word" with double quotes.

You could switch identifier delimiter on and off at runtime - but don't! It becomes an insane mess to keep app alive.

Code samples:

// Example Table ---------------------------------------------------------------
create table TEST(ID int IDENTITY, NAME nvarchar(50), [ORDER] int, constraint _ primary key (ID));

// DB connection setup (MSSQL 2019) --------------------------------------------
SQLCA.DBMS = "SNC"
SQLCA.DBParm = "...,DelimitIdentifier=1"
CONNECT USING SQLCA;

// Embedded SQL ----------------------------------------------------------------
INSERT INTO TEST(NAME, "ORDER") VALUES ('Test embedded SQL', 4);
SELECT newID INTO :id FROM (SELECT SCOPE_IDENTITY() newID) data;
COMMIT;

SELECT count(*) INTO :ll_count FROM TEST WHERE "ORDER" = 4;

// Using DataWindow in DataStore -----------------------------------------------
/* DW's SQL Painter */ SELECT ID, NAME, [ORDER] FROM TEST
/* Generated SELECT */ SELECT ID, NAME, [ORDER] FROM TEST
/* Generated INSERT */ INSERT INTO "TEST" ( "NAME", "ORDER" ) VALUES ( 'Test via DW SQL', 4 )

HTH /Michael

Am still going through a database migration from SYBASE ASE to SQL Server.  Had a very similar issue.  The best thing to do is to bite the bullet and rename the column.  You are much better off in the long run.

Have you tried using double quotes around the column name? By using double quotes, "order" will tell the parser that it's a table/column name and not a keyword.

In general, it's a bad idea to use keywords as table or column names, and should be avoided if possible.