Re: Preventing Duplicate Data WAS UUID vs Longint primary key

Chip: I have always tried doing at the point of data entry. Obviously no code is perfect, and either is the object between the keyboard and the chair. My experience is that few Administrators would take the time to filter through duplicates. Getting them to do system maintenance was almost

Re: Preventing Duplicate Data WAS UUID vs Longint primary key

Jody, what are your normal duplicate reducing/removal technic(s)? On Mon, 7 Aug 2017 12:28:21 -0600, Jody Bevan via 4D_Tech wrote: > John: > > Thanks for sharing this. I had not thought of this way after all > these years. I will take the idea and apply where appropriate, in > addition to my

Re: ​Re: Preventing Duplicate Data WAS UUID vs Longint primary key

I've found that after hours "helper" routines that fire off and run in the > background working through data to flag dupes for admin oversight next day is > popular with some managers who prefer to make their own decision about whether > some stuff really is a dupe or not. Some duplicate data has

​Re: Preventing Duplicate Data WAS UUID vs Longint primary key

On Mon, Aug 7, 2017 at 3:00 PM, ​ ​ David Adams wrote: > > > > How do you deal with that problem (Preventing duplicate data) > Definitely ​ "Carefully program your system to detect and prevent duplicate rows" as appropriate. Generally such a Dupe Check can take many forms

Re: Preventing Duplicate Data WAS UUID vs Longint primary key

As a variant on John's technique, I'll combine fields into a single text block that I then run through a fast hashing algorithm that returns a longint. What good is that longint? It helps in two cases: * If you're comparing two copies of the same record during an update/sync, etc., then you can

Re: Preventing Duplicate Data WAS UUID vs Longint primary key

John: Thanks for sharing this. I had not thought of this way after all these years. I will take the idea and apply where appropriate, in addition to my normal code to reduce duplicates. Jody Bevan ARGUS Productions Inc. Developer Argus Productions Inc.

Re: Preventing Duplicate Data WAS UUID vs Longint primary key

What I have done is to have a field in the table that contains the keys that make the record unique with all spaces, special characters, and vowels removed, as well as eliminating any consecutive consonants . See my example below. So far this has worked pretty well for me and I guess would

Re: Preventing Duplicate Data WAS UUID vs Longint primary key

perhaps you can use sounded and store that in a hidden field. Regards Chuck Chuck Miller Voice: (617) 739-0306 Informed Solutions, Inc. Fax: (617) 232-1064