[FX.php List] case sensitive query + indexing question]

[Joel Shapiro]

Hi Derrick

I agree that using the RecID that comes through FX.php is preferable,  
although I believe it's necessary to have a RecID field when you need  
to edit related records since FX doesn't give the data key for those  
records -- only for the parent records (whose table the layout is  
based on)

(Gee, could I have found a *more* awkward way to say that?)

And yes, I can see possible issues w/ stored RecIDs and imports.   
Good point.

-Joel


On Jul 20, 2007, at 6:24 AM, Derrick Fogle wrote:

> One would hope. But I'd want Alex to search his memory on why the  
> indexing - and what about storage? - was turned off. I've seen a  
> stored FM RecID calc field get out-of-synch in instances were I was  
> importing data from one version of a database to another. To that  
> end, I would recommend always using the RecID that comes as part of  
> the data key if you need to update a record. I have more faith that  
> one is right.
>
> On Jul 19, 2007, at 7:01 PM, Joel Shapiro wrote:
>
>> I can't think of a good reason to have indexing off on a calc  
>> field like RecID, since that should unchanging.
>
>
> Derrick Fogle
> derrick at fogles.net
>
>
>
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list