Data Access Worldwide Knowledge Base

Article ID 2253
Article Title ERROR: "Command not found FLEX$INIT" when compiling new Visual DataFlex program
Article URL http://www.dataaccess.com/kbasepublic/KBPrint.asp?ArticleID=2253
KBase Category VDF (GENERAL)
Date Created 10/25/2006
Last Edit Date 10/25/2006


Article Text
QUESTION:
I created a new workspace and in there a new project, a web project. When I compile this project the compiler gives the following errors:

----Compiler Error Summary----
Error 4298: C:\Visual DataFlex Projects\Test\AppSrc\WebApp.src (ln 0) Command not found FLEX$INIT
Error 4298: C:\Visual DataFlex Projects\Test\AppSrc\WebApp.src (ln 1) Command not found USE
Error 4298: C:\Visual DataFlex Projects\Test\AppSrc\WebApp.src (ln 3) Command not found OBJECT
Error 4298: C:\Visual DataFlex Projects\Test\AppSrc\WebApp.src (ln 4) Command not found END_OBJECT
Error 4298: C:\Visual DataFlex Projects\Test\AppSrc\WebApp.src (ln 6) Command not found OBJECT
Error 4298: C:\Visual DataFlex Projects\Test\AppSrc\WebApp.src (ln 7) Command not found USE
Error 4298: C:\Visual DataFlex Projects\Test\AppSrc\WebApp.src (ln 19) Command not found END_OBJECT
Error 4298: C:\Visual DataFlex Projects\Test\AppSrc\WebApp.src (ln 21) Command not found SEND
Error 4348: C:\Visual DataFlex Projects\Test\AppSrc\WebApp.src (ln 22) Unresolved control block

What is wrong here? I can compile the example applications without problems.

ANSWER:
The DataFlex compiler uses a file called FLEX.CFL, a compiled command library, that stores the commands that are allowed in the language.

The above errors indicate that the compiler found a FLEX.CFL where the instructions used in the program being compiled could not be found. To fix this error, review the content of the directories specified for your workspace (in its WS file) -- e.g. the workspace DataPath setting could point to a directory that contains a FLEX.CFL from a different version of DataFlex.

Note:
In this specific case, it was confirmed that the DataPath was mapped to the FLEX23 directory and that the same tables plus the filelist that was used in a legacy application needed to be used in the web application.

To solve the problem, the FLEX.CFL was renamed so that it cannot be found by Visual DataFlex. The DataFlex 2.3b application will continue to run without problems; it will only not compile -- for that, the file will need to be renamed back to FLEX.CFL.



Contributed By:
Vincent Oorsprong
Company: Data Access Worldwide
email: vincent.oorsprong@dataaccess.eu
Web Site: http://www.dataaccess.eu


Email this Article
Email this Article to a Colleague
Send Feedback on this Article to Data Access Worldwide
Copyright ©2010 Data Access Corporation. All rights reserved.

The information provided in the Data Access Technical Knowledge Base is provided "as is" without warranty of any kind. Data Access Corporation disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Data Access Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Data Access Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.