Problem with Forms->Pls. help

Hello, I am Rick and I work as a DBA in one of our client's office. I have one simple question for you that I consider complex on my part since I'm a new DBA. An informix form(V 6.0) can't be run due to an alteration of a column type. Same test in Version 4.0 prooves that when I put back the original type the form will work w/o compiling. I tried all data types but it gives error that form must be rebuild. But, I noticed one thing. Comparing the structure of DBSCHEMA between version 4 and 6 shows that there is an extra not null constraint nXXX_XXX where XXX_XXX is unique number on every DB alteration. This is not present in V4.0. My question is that could this be a reason why I can't run my form after altering all changes in column type ? May God Bless You for reading this e-mail... Best Regards, Rick Pusong - UNIX DBA --------------------------------------------------- Get free personalized email at http://www.iname.com

fredricke@iname.com wrote: > > Hello, I am Rick and I work as a DBA in one of our client's office. I have one simple question for you that I consider complex on my part since I'm a new DBA. > > An informix form(V 6.0) can't be run due to an alteration of a column type. Same test in Version 4.0 prooves that when I put back the original type the > form will work w/o compiling. I tried all data types but it gives error that form must be rebuild. But, I noticed one thing. Comparing the structure of DBSCHEMA between version 4 and 6 shows that there is an extra not null > constraint nXXX_XXX where XXX_XXX is unique number on every DB alteration. > This is not present in V4.0. > > My question is that could this be a reason why I can't run my form after altering all changes in column type ? I don't think so unless the column is not NOT NULL in the 4.xx version. Originally in SQL NOT NULL was a column attribute later ANSI rules made NOT NULL a column constraint and although Informix still accepts the older syntax, which I prefer FWIW, dbschema in later engine versions outputs the NOT NULL attribute as a CONSTRAINT to comply. Art S. Kagel