There's certainly a bug in the compiler; doing
d $System.OBJ.CompileAll("f")
we get this error log (cut & pasted):Compiling table SQLUser.BookOfferta ... Compiling table SQLUser.FinanceClifor ... (...) Compiling view SQLUser.BookOffertaClosure ... ERROR #5521: Errore SQL: -30:Error occurred compiling view SQLUser.BookOffertaCl osure's query. %msg = SQL ERROR #30: Table `SQLUSER.BOOKOFFERTA' not found^er r = qaqperr^ Compiling view SQLUser.AnalisiChiamate ... Compiling view SQLUser.MovimentiEsterni ... ERROR #5521: Errore SQL: -30:Error occurred compiling view SQLUser.MovimentiEste rni's query. %msg = SQL ERROR #30: Table `SQLUSER.FINANCECLIFOR' not found^er r = qaqperr^ Compiling view SQLUser.AnalisiContratti ... As you can see, the class is compiled, but the view complains that it can't find it! This is not a precedence trouble, since it's correctly compiled *before*. Max "Ram�n Jim�nez" <[EMAIL PROTECTED]> ha scritto nel messaggio news:[EMAIL PROTECTED] > Sukesh, > > > Max & Peter > > > > I do not think the problem is with dependencies and relationships. > > > > The problem may that classes imported are not getting registered correctly > > for the compiler to know of their existence. > > (This may be a bug). > > I would not rule out that in some circumstances it may actually be both :) > > Looking forward to your feedback! > > Ram�n
