DBCENTURY and 4GL and ISQL

Hi, we are working with IDS 7.3, ISQL 6.04. If we set DBCENTURY=C, then INSERTs with dbaccess are working well, as we expected it, but the DATE-fields in the ISQL-Forms expand 2-digit Years allqays with "19". On page 45 of Tech Notes, Volume 8, Issue 3, 1998, June Tong wrote: "Similarly, for input performed through a 4GL PROMPT statement or form, if the receiving variable is defined as a DATE datatype, the century expansion is accomplished at the point where the data is placed in the variable, and the DBCCENTURY value is taken from the client." It seems, that this is not true. Who can help me? Christian Winterhager

Christian, Unfortunately there are NO V6 tools that support DBCENTURY ! You will need I-SQL and 4GL at Version 7.20 which are the first ones to support DBCENTURY. For anyone working with version 5 engine and 4 tools, SE V5.10 is the first to support DBCENTURY along with SQL and 4GL at Verions 4.20. I am aware of the following being the earliest versions of each product to support DBCENTURY. Informix SE V5.10 V7.20 Informix Online V5.10 Informix IDS V7.20 Informix I-SQL V4.20 V7.20 Informix I-4GL/R-4GL V4.20 V7.20 At the point where the tools changed from 6.x to 7.20 is where the DBCENTURY was introduced so V6.x does not and will never support DBCENTURY. Informix has not always been clear in this message. In article <7cj87q$n8t$1@news.xmission.com>, Christian Winterhager <christian.winterhager@orbit.de> wrote: > > Hi, > > we are working with IDS 7.3, ISQL 6.04. If we set DBCENTURY=C, then > INSERTs with dbaccess are working well, as we expected it, but the > DATE-fields in the ISQL-Forms expand 2-digit Years allqays with "19". > > On page 45 of Tech Notes, Volume 8, Issue 3, 1998, June Tong wrote: > "Similarly, for input performed through a 4GL PROMPT statement or form, > if the receiving variable is defined as a DATE datatype, the century > expansion is accomplished at the point where the data is placed in the > variable, and the DBCCENTURY value is taken from the client." > > It seems, that this is not true. > > Who can help me? > > Christian Winterhager > > -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

C is for closest century (past, current or future) to the current date. Did you try '01 thru 49?' My guess is that those would expand to 21st century dates. Is this not the case in 4gl? What are examples of the data you entered? In article <7cj87q$n8t$1@news.xmission.com>, Christian Winterhager <christian.winterhager@orbit.de> wrote: > > Hi, > > we are working with IDS 7.3, ISQL 6.04. If we set DBCENTURY=C, then > INSERTs with dbaccess are working well, as we expected it, but the > DATE-fields in the ISQL-Forms expand 2-digit Years allqays with "19". > > On page 45 of Tech Notes, Volume 8, Issue 3, 1998, June Tong wrote: > "Similarly, for input performed through a 4GL PROMPT statement or form, > if the receiving variable is defined as a DATE datatype, the century > expansion is accomplished at the point where the data is placed in the > variable, and the DBCCENTURY value is taken from the client." > > It seems, that this is not true. > > Who can help me? > > Christian Winterhager > > -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

If the DBCENTURY variable wasn't exported, then it won't be set for a 4gl program running in a new shell process. That being the case, Informix will default to "R" for recent century, which will cause any two digit year to be expanded to the current century. Mike Mabin In article <7cj87q$n8t$1@news.xmission.com>, Christian Winterhager <christian.winterhager@orbit.de> wrote: > > Hi, > > we are working with IDS 7.3, ISQL 6.04. If we set DBCENTURY=C, then > INSERTs with dbaccess are working well, as we expected it, but the > DATE-fields in the ISQL-Forms expand 2-digit Years allqays with "19". > > On page 45 of Tech Notes, Volume 8, Issue 3, 1998, June Tong wrote: > "Similarly, for input performed through a 4GL PROMPT statement or form, > if the receiving variable is defined as a DATE datatype, the century > expansion is accomplished at the point where the data is placed in the > variable, and the DBCCENTURY value is taken from the client." > > It seems, that this is not true. > > Who can help me? > > Christian Winterhager > > -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own