Micro Focus Enterprise Developer 3.0 for Visual Studio 2013 > Welcome > Product Information > Known Issues and Restrictions > Data Access > COBSQL

COBSQL

If an Embedded SQL statement has a comment in columns 73 - 80 and is not terminated by a period, the Oracle precompiler (Pro*Cobol) considers the next COBOL line as part of the Embedded SQL statement and comments it out.
To prevent this making COBSQL hang, use the COBSQL directive SQLDEBUG. Then, when COBSQL encounters such a line, it displays:
```
CSQL-W-040: Pro*Cobol commented out the following line 
```
The program logic is altered because Pro*Cobol has commented out a COBOL line. We recommend, therefore, that you do not execute programs that produce this message. You should either remove the comment text or terminate the Embedded SQL statement with a period.
Using sequence numbers inside Sybase Embedded SQL statements causes COBSQL to lose its position in the source. This leads to the message "Premature end of expanded source" being displayed and means the code cannot be checked.
If an EXEC WHENEVER ... END-EXEC or an EXEC DECLARE ... END-EXEC statement is the last statement in a paragraph or section, you may get a compilation error on the name of the following paragraph. If this happens, place an extra COBOL sentence (terminated by a period) after the WHENEVER or DECLARE statement. For example:
```
CONTINUE.
```
When Pro*COBOL is not installed on your local machine and you are using the local machine to access an Eclipse project on a remote machine that does have Pro*COBOL installed, background parsing can fail during compilation. You can avoid this by setting the COBSQL directive either in your Eclipse project properties, or by coding a $SET statement into the source itself. However, if you prefer to specify the COBSQL directive in a directive file only, you must specify the SQLBGP compiler directive option in the directive file as well. For example:
```
p(cobsql) SQLBGP MAKESYN CSQLT=ORACLE8 end-c p(cp) endp
```