BUG: Invalid ALTER TABLE Command Works and Corrupts DBC

      CLOSE DATABASE ALL
      USE testdb.DBC
      DELETE FOR objectid=14 &&Delete object #14's record
      PACK
      USE
				

MORE INFORMATION

The ALTER TABLE command allows the entry of an Add Foreign Key statement without specifying an expression. This causes an invalid entry in the database referencing a relationship that does not exist. This causes the VALIDATE DATABASE command to return the following error:

Steps to Reproduce Behavior

1. Run the following code in a program file:

         #DEFINE DBCNAME    'testdb'
         #DEFINE TABNAME    'testtab'
         #DEFINE TABCOUNT      2
   
         CLEAR
         CLOSE DATA ALL
         DELETE FILE testdb.DBC
         DELETE FILE testdb.dc?
   
         CREATE DATABASE DBCNAME
   
         FOR lni = 1 TO TABCOUNT
            DELETE FILE (TABNAME+ALLTR(STR(lni)))+'.dbf'
            DELETE FILE (TABNAME+ALLTR(STR(lni)))+'.cdx'
            CREATE TABLE (TABNAME+ALLTR(STR(lni))) (F1 C(10) NOT NULL ;
               PRIMARY KEY, ;
               F2 C(10) NOT NULL)
         ENDFOR
   
         * Gives invalid DBC because Foreign key expression is missing
         ALTER TABLE (TABNAME+("2")) ADD FOREIGN KEY TAG ;
            F2 REFERENCES (TABNAME+"1") TAG F1
   						

2. Issue the "VALIDATE DATABASE" command from the Command window. Note that this command returns the following error:
   "Object #14 (Relation 'Relation 1'): Cannot find associated Index referenced by this object"