Maybe useful to provide a little bit more details on your issue... 
For example:

• Micro Focus product / version / update level?
• Which DBMS?
• Used pre-processor?
• SQL statement failing?
• ...  (all other meaningful information to help for resolution)

Thanks and Happy New Year,

Daniel

I am afraid Carlo that without any more details regarding your precise development/execution environment nobody will be able to help you.
You are far to much vague in your description.
For example, when you say "on a db2 table", what is the underlying DBMS that is used?  DB2 z/OS via XDB Link?  DB2 z/OS via DB2Connect? DB2 LUW? XDB (SQL Option)? Other (SQL Server?, ...) ?  COBOL Native code?  Managed code? ...   32/64 bit?  ...

Can you also provide answers about my initial questions?

Thanks,

Daniel

I am afraid Carlo that without any more details regarding your precise development/execution environment nobody will be able to help you.
You are far to much vague in your description.
For example, when you say "on a db2 table", what is the underlying DBMS that is used?  DB2 z/OS via XDB Link?  DB2 z/OS via DB2Connect? DB2 LUW? XDB (SQL Option)? Other (SQL Server?, ...) ?  COBOL Native code?  Managed code? ...   32/64 bit?  ...

Can you also provide answers about my initial questions?

Thanks,

Daniel

Sorry Daniel,
if I don't answer everything is because I ignore a lot of answers to your questions.
However I will try to do it

• Micro Focus product / version / update level?

I'm using Visual COBOL for Visual Studio Personal Edition

• 
  Which DBMS?

I've connected my microsoft office access database(.mdb) through ODBC(see attachment)

Used pre-processor?

I'm sorry but I do not know what to answer

SQL statement failing?

MOVE WRAGSOC to K-RAGSOC
MOVE WPIVA to K-PIVA
MOVE WCF to K-CF

EXEC SQL
SELECT
`A`.`CLI-cod`
,`A`.`CLI-ragsoc`
,`A`.`CLI-ind`
,`A`.`CLI-loc`
,`A`.`CLI-prov`
,`A`.`CLI-cap`
,`A`.`CLI-piva`
,`A`.`CLI-tel`
,`A`.`CLI-fax`
,`A`.`CLI-email`
,`A`.`CLI-web`
,`A`.`CLI-cf`
INTO
:TABCLI-001:TABCLI-001-NULL
,:TABCLI-002:TABCLI-002-NULL
,:TABCLI-003:TABCLI-003-NULL
,:TABCLI-004:TABCLI-004-NULL
,:TABCLI-005:TABCLI-005-NULL
,:TABCLI-006:TABCLI-006-NULL
,:TABCLI-007:TABCLI-007-NULL
,:TABCLI-008:TABCLI-008-NULL
,:TABCLI-009:TABCLI-009-NULL
,:TABCLI-010:TABCLI-010-NULL
,:TABCLI-011:TABCLI-011-NULL
,:TABCLI-012:TABCLI-012-NULL
FROM `TABAZ` A

WHERE ( `CLI-ragsoc` = :K-RAGSOC
AND `CLI-piva` = :K-PIVA
AND `CLI-cf` = :K-CF)
END-EXEC

I hope you have more information to help me

Thanks

Carlo

Yes.  If your table name is incorrect and does not exist in your MDB database, you will get an error when executing the SELECT.

What else to check in case of trouble:

• Successful execution of the CONNECT statement
• Content of sqlerrmc COBOL field
• ODBC Tracing output
  (Enabled via the ODBC Data Source Admistrator.  Tab "Tracing")

Good luck,

Daniel

Yes.  If your table name is incorrect and does not exist in your MDB database, you will get an error when executing the SELECT.

What else to check in case of trouble:

• Successful execution of the CONNECT statement
• Content of sqlerrmc COBOL field
• ODBC Tracing output
  (Enabled via the ODBC Data Source Admistrator.  Tab "Tracing")

Good luck,

Daniel