Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

Flexible defining of join-properties

Discussion in 'Information Technology' started by Medioman, Jul 28, 2006.

  1. Medioman

    Medioman
    Expand Collapse
    Guest

    Hi everybody,

    I've a problem with the so-called join properties.
    Within the design field, I have defined a relationship between a query and
    a table:

    Query: all_city_names Table: selected_city_names
    Fieldname: Cityname <--> Fieldname: Cityname

    So I want to filter out the city names from the query "all_city_names" on
    the basis of city names which are definied in the table (i.e.
    selected_city_names). In principle Access can easily execute this command.

    However, some problems arise with records which contains some spelling
    mistakes / differences.

    First example:

    The query contains a record with the city name "Vancouve", while the
    definied table only contains the city name "Vancouver".
    Result: "Vancouve" isn't filtered out, because of the missing "r"-term.

    Second example:

    The query contains a record with the city name "NewYork", while the definied
    table only contains the city name "New York".
    Result: "NewYork" isn't filtered out, because of the missing "space".

    Therefore my question is: how to configure a flexibele join-property
    relationship which is able to deal with small spelling mistakes /
    differences?
    Or in other words: is it possible to filter out the asked city records on
    the basis of high similarity of characters?


    Many thanks!

    Medioman
     
  2. Loading...

    Similar Threads Forum Date
    Defining a Sikh Essays on Sikhism Feb 21, 2013
    Controversial Defining Authority in Sikhism Hard Talk Oct 23, 2015
    Buddhism Buddhism and Wealth: Defining 'Right Livelihood' Interfaith Dialogues Mar 20, 2011
    Re-defining Sikh Activism Sikh Sikhi Sikhism Oct 17, 2009
    Re-defining Sikh, Sikhi Sikhism Interfaith Dialogues May 17, 2005

  3. Douglas J Steele

    Douglas J Steele
    Expand Collapse
    Guest

    One possibility is to use Soundex.

    I wrote about this (and another similar technique, Levenshtein Distance) in
    my April 2005 "Access Answers" column in Pinnacle Publication's "Smart
    Access". You can download the column (and sample database) for free at
    http://www.accessmvp.com/DJSteele/SmartAccess.html

    --
    Doug Steele, Microsoft Access MVP
    http://I.Am/DougSteele
    (no e-mails, please!)


    "Medioman" <medioman@discussions.microsoft.com> wrote in message
    news:6aab3$44638259$54565128$13744@news2.tudelft.nl...
    > Hi everybody,
    >
    > I've a problem with the so-called join properties.
    > Within the design field, I have defined a relationship between a query and
    > a table:
    >
    > Query: all_city_names Table: selected_city_names
    > Fieldname: Cityname <--> Fieldname: Cityname
    >
    > So I want to filter out the city names from the query "all_city_names" on
    > the basis of city names which are definied in the table (i.e.
    > selected_city_names). In principle Access can easily execute this command.
    >
    > However, some problems arise with records which contains some spelling
    > mistakes / differences.
    >
    > First example:
    >
    > The query contains a record with the city name "Vancouve", while the
    > definied table only contains the city name "Vancouver".
    > Result: "Vancouve" isn't filtered out, because of the missing "r"-term.
    >
    > Second example:
    >
    > The query contains a record with the city name "NewYork", while the

    definied
    > table only contains the city name "New York".
    > Result: "NewYork" isn't filtered out, because of the missing "space".
    >
    > Therefore my question is: how to configure a flexibele join-property
    > relationship which is able to deal with small spelling mistakes /
    > differences?
    > Or in other words: is it possible to filter out the asked city records on
    > the basis of high similarity of characters?
    >
    >
    > Many thanks!
    >
    > Medioman
    >
    >
    >
     
  4. xRoachx

    xRoachx
    Expand Collapse
    Guest

    Hi -- This problem can be solved by your design. For example, rather than
    allow users to free type the city names, you should use a combo box
    (cascading) or list box so they can choose the name and the key is stored.
    This way you can do joins on the key. However, this may not be possible if
    there are too many cities for you to manage but is the best way to go.

    Another option is to use the Like statement as critieria to attempt to
    capture the spelling differences. However, by allowing free typing you'll
    never be able to capture them all. For example: NewYork, New York,
    NY...include misspelling and it gets worse!

    "Medioman" wrote:

    > Hi everybody,
    >
    > I've a problem with the so-called join properties.
    > Within the design field, I have defined a relationship between a query and
    > a table:
    >
    > Query: all_city_names Table: selected_city_names
    > Fieldname: Cityname <--> Fieldname: Cityname
    >
    > So I want to filter out the city names from the query "all_city_names" on
    > the basis of city names which are definied in the table (i.e.
    > selected_city_names). In principle Access can easily execute this command.
    >
    > However, some problems arise with records which contains some spelling
    > mistakes / differences.
    >
    > First example:
    >
    > The query contains a record with the city name "Vancouve", while the
    > definied table only contains the city name "Vancouver".
    > Result: "Vancouve" isn't filtered out, because of the missing "r"-term.
    >
    > Second example:
    >
    > The query contains a record with the city name "NewYork", while the definied
    > table only contains the city name "New York".
    > Result: "NewYork" isn't filtered out, because of the missing "space".
    >
    > Therefore my question is: how to configure a flexibele join-property
    > relationship which is able to deal with small spelling mistakes /
    > differences?
    > Or in other words: is it possible to filter out the asked city records on
    > the basis of high similarity of characters?
    >
    >
    > Many thanks!
    >
    > Medioman
    >
    >
    >
    >
     

Share This Page