Rx_
Nothing In Moderation
- Local time
- Today, 00:48
- Joined
- Oct 22, 2009
- Messages
- 2,795
Ideas welcome: My Problem -- A table tracks site names in a single text field (with an auto counter for the primary key).
There is a loose business rule to enter a new site name based on some fuzzy rules. So, as new sites are added there are business naming duplicates when people don't communicate.
Example: Critter Well NV 033 <--- > Critter 33 Wells NV could be entered by two different offices and refer to the same site.
These are not actual Database duplicates, but represent a business site naming duplicate. It creates the same kind of problems.
Solution sought: So, as someone enters a new site name, the idea is to use a function to produce some output of all simular names so users can determine that site name already exist. Maybe like a Yahoo search "You typed "<blaa>" did you mean... <bla> or <BllA>
With offices across the nation, when two people enter a new site name, there are 45 associated forms to track other things about that business site. And when they discover the duplicate site name a month later, they just want the database guy to merge the different data (and often conflicting data). With a 1,000 new sites a month across 5 offices, duplicates are growing. Names like "Robert" vs. "Bob" are not an issue since the sites somewhat describe a legal description of sorts.
At least it is a single text field.
If anyone has ideas, please share. In a couple of weeks, I hope to post my solution.
There is a loose business rule to enter a new site name based on some fuzzy rules. So, as new sites are added there are business naming duplicates when people don't communicate.
Example: Critter Well NV 033 <--- > Critter 33 Wells NV could be entered by two different offices and refer to the same site.
These are not actual Database duplicates, but represent a business site naming duplicate. It creates the same kind of problems.
Solution sought: So, as someone enters a new site name, the idea is to use a function to produce some output of all simular names so users can determine that site name already exist. Maybe like a Yahoo search "You typed "<blaa>" did you mean... <bla> or <BllA>
With offices across the nation, when two people enter a new site name, there are 45 associated forms to track other things about that business site. And when they discover the duplicate site name a month later, they just want the database guy to merge the different data (and often conflicting data). With a 1,000 new sites a month across 5 offices, duplicates are growing. Names like "Robert" vs. "Bob" are not an issue since the sites somewhat describe a legal description of sorts.
At least it is a single text field.
If anyone has ideas, please share. In a couple of weeks, I hope to post my solution.