|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||||||
|
|||||||||||||||||
|
|||||||||||||||||
|
|||||||||||||||||
|
|
|
|
||
|
|
|
| [an error occurred while processing this directive] | |
 ENTERA DEVELOPER SUPPORT
Frequently Asked Questions Problems with comments in SQL file Question: I'm getting SQL warnings when running SQLmake on my SQL file after migrating to Entera 3.2. Why does this happen? Answer: Entera 3.2 has problems parsing particular comments in SQL files. In general the problem occurs when the comment is embedded in a SQL query (between the function tag and the query), and the first character after the # sign is not a space. You should workaround this problem by removing the comments, moving them outside the function blocks, or adding a space immediately after the # sign.
|
|
||
|
|
|
|
||
|
|
|
|
 |
||
|
||
| Made in Borland® Copyright© 1994-2003 Borland Software Corporation. All rights reserved. Last Modified Friday, 23-Mar-2001 17:07:03 PST |
||
