Re: Same options in i4gl, dbaccess & upscol?

>The DB-Access constraints should be specified when the table is created, >but will not be enforced by UPSCOL or the form system -- the form system >and UPSCOL predate the database-enforced constraints, so it is unaware that >they exist and does not know it should look for them. It would be sensible >to have that ability, but that would require changes to I4GL. So, when I use INPUT DEFAULT for a screen, none of the default/constraint work I've done at the table/column level thru dbaccess will show up. Hearty implementation of data rules requires work at both column and screen levels, right? This appears to be true even for primary key information and referential integrity? Since these utilities are not well integrated with each other I wonder if one might be inclined to not use them so much, and opt for data validation thru code (i4gl) instead. That way one can "see" what is going on all in one place instead of trying to guess at what level rules have been implemented. Or, maybe attention to detail thru the utilities is really worth the effort, in order to insure solid data. I'm working on the time stamp field on a screen form and am getting "00:00". My column is datetime hour to second as you suggested. The upscol default is CURRENT. I tried "default = current" at the form (*.per) level and still no luck: "00:00". Thru dbaccess query-language I INSERTed a row and received the proper time stamp (implemented thru dbaccess Defaults option). What have I missed? Thanks, Nelson Nelson Fredsell Cornerstone Capital Atlanta, GA nfredsel@cornercap.com