My test program uses OPENCHECK so the setting if this parameter should not be having any effect. However, just to stoke the fire, I have verified via uvconfig & >CONFIG DATA that we do have OPENCHK set to '1' !! So we should be seeing data constraint errors being reported by OPEN/WRITE , OPENCHECK/WRITE & ICHECK !!
I have written up a summary and sent it off to the client's sys admin to pass on to their universe support. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Clifton Oliver Sent: April 29, 2008 5:56 PM To: [email protected] Subject: Re: [U2] UniVerse SQL Tables The parameter is OPENCHK. "OPENCHK - the modifies the behavior of operations upon files open via the BASIC OPEN statement. When set to zero, I/O to files open with the BASIC OPEN statement ignore integrity constraints. If non- zero those files will observe the constraints. This tunable does not affect files opened via the OPENCHECK statement." Regards, Clif -- W. Clifton Oliver, CCP CLIFTON OLIVER & ASSOCIATES Tel: +1 619 460 5678 Web: www.oliver.com On Apr 29, 2008, at 1:56 PM, David Jordan wrote: > Hi Gerry > > I think there is an option in UvConfig that allows bad data to be > written to > a table despite constraints. I have not been able to write bad > data to an > SQL Table as you have done in the test program. > > Regards > > David Jordan > > Managing Consultant > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
