RE: [Hardhats-members] field uniqueness (key index but null allowed)

2006-03-08 Thread Dan
So kinda still at square one -- don't know how (or if) FM will handle changing the field in the middle of generating xrefs and how to do this (whether to call FM to set the field value to empty or to use @ to delete the field while inside the xref fire). Guess I'll have to do some

Re: [Hardhats-members] field uniqueness (key index but null allowed)

2006-03-08 Thread Steven McPhelan
I will have to look. Isn't there a file DDnode that will run a routine in the pre-edit stage prior to actually doing the edit. I also vaguely remember that there was a way to get FM to quit the edit session at that point. This is all from memory. On 3/8/06, Dan [EMAIL PROTECTED] wrote: So kinda

RE: [Hardhats-members] field uniqueness (key index but null allowed)

2006-03-07 Thread Cameron Schlehuber
@lists.sourceforge.net Subject: RE: [Hardhats-members] field uniqueness (key index but null allowed) For each record the field could either have a value or could be empty -- more than one record could have the field empty. If the field has a value the value has to be unique within the other records that have

RE: [Hardhats-members] field uniqueness (key index but null allowed)

2006-03-07 Thread Dan
Aren't Input Transforms only executed when passing external values via FileMan DB calls? At 01:41 PM 3/7/2006, Cameron wrote: A simple regular cross-reference on the field could keep track of all values used in that field. Put your logic in the Input Transform. Note that the SSN field in

Re: [Hardhats-members] field uniqueness (key index but null allowed)

2006-03-07 Thread James Gray
07, 2006 12:43 PM Subject: RE: [Hardhats-members] field uniqueness (key index but null allowed) Aren't Input Transforms only executed when passing external values via FileMan DB calls? At 01:41 PM 3/7/2006, Cameron wrote: A simple regular cross-reference on the field could keep track of all

RE: [Hardhats-members] field uniqueness (key index but null allowed)

2006-03-07 Thread Cameron Schlehuber
: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James Gray Sent: Tuesday, March 07, 2006 1:51 PM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] field uniqueness (key index but null allowed) You aren't planning to put data into this field any other way than through

Re: [Hardhats-members] field uniqueness (key index but null allowed)

2006-03-07 Thread Steven McPhelan
PROTECTED] To: hardhats-members@lists.sourceforge.netSent: Tuesday, March 07, 2006 12:43 PMSubject: RE: [Hardhats-members] field uniqueness (key index but null allowed) Aren't Input Transforms only executed when passing external values via FileMan DB calls? At 01:41 PM 3/7/2006, Cameron wrote:A

RE: [Hardhats-members] field uniqueness (key index but null allowed)

2006-03-07 Thread Cameron Schlehuber
Three ways! Thanks, Steve! Cameron -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steven McPhelan Sent: Tuesday, March 07, 2006 4:18 PM To: hardhats-members@lists.sourceforge.net Subject: Re: [Hardhats-members] field uniqueness (key

RE: [Hardhats-members] field uniqueness (key index but null allowed)

2006-03-07 Thread Dan
That's the whole problem -- if another programmer uses a db call with internal values then the Input Transform rules would be bypassed, leading to the possibility of duplicate entries. One could provide a special API for handling that field but once again if somebody doesn't use that API

RE: [Hardhats-members] field uniqueness (key index but null allowed)

2006-03-07 Thread Cameron Schlehuber
@lists.sourceforge.net Subject: RE: [Hardhats-members] field uniqueness (key index but null allowed) That's the whole problem -- if another programmer uses a db call with internal values then the Input Transform rules would be bypassed, leading to the possibility of duplicate entries. One could provide a special

[Hardhats-members] field uniqueness (key index but null allowed)

2006-03-05 Thread Dan
What's the best way to enforce field uniqueness when the field is allowed to be null? This should work whether data is being entered manually or by FileMan APIs (internal value which means input transform isn't useable). I'm looking for the behavior of a key index but that allows for null

RE: [Hardhats-members] field uniqueness (key index but null allowed)

2006-03-05 Thread Cameron Schlehuber
Of Dan Sent: Sunday, March 05, 2006 4:20 PM To: hardhats-members@lists.sourceforge.net Subject: [Hardhats-members] field uniqueness (key index but null allowed) What's the best way to enforce field uniqueness when the field is allowed to be null? This should work whether data is being entered

RE: [Hardhats-members] field uniqueness (key index but null allowed)

2006-03-05 Thread Dan
: Sunday, March 05, 2006 4:20 PM To: hardhats-members@lists.sourceforge.net Subject: [Hardhats-members] field uniqueness (key index but null allowed) What's the best way to enforce field uniqueness when the field is allowed to be null? This should work whether data is being entered manually