Access 2013 - Bridging of similar but different data sets.

I have a project to develop a process to manage out bound phone calls, track the results and follow up work, etc.

These calls are defined through 2 separate programs, so the data I need, while being the same, come to me in different formats.
Example: Names in one system are JOE JONES, while the other is Jones, Joe.  Phone numbers in one are (xxx) xxx-xxxx and xxxxxxxxxx in the other.

Looking for best practices to melt these two data streams together into a single process, while being able to track the caller, time called, results, etc.


Thanks again for your expertise!
Dennis
DGWhittakerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
If there is no need for anything to go back into the programs involved, then what you do with your app makes little difference.  One way or another, you'll have to massage the data of one or the other (or possibly both) to import it into your app.   That's not a major hurdle.

 I would design your DB the way that it will work best, then worry about pulling in the data after that.  You could very easily find for example that you'll import one external file, but the data ends up in more than one table within your app.

Jim.
0
Jeffrey CoachmanMIS LiasonCommented:
1. Also, lets be clear on what you mean by "Bridging"...
...Do you mean "Matching" (ex: "Joe, jones" = "jones, joe", ...123-456-7890=1234567890)
If so, then you may have to consider things like Upper/Lower case, leading/trailing unprintable characters, and even outright misspellings, ...etc

2. In both of your "name" scenarios, ...are both the first and last names stored in separate fields? (or are they both store in one field)

3. In cases like this, misspellings will almost certainly be the biggest obstacle to "matching" records.

4. Finally you may have to consider "combinations" of matching fields:
ex:
Jones, Joe, 631-216-9876 vs Joe, Jones, 631-216-2765
Here there is a match on the name(s) , but not on the phone umber...
....what of records like this?

JeffCoachman
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
hnasrCommented:
May you upload a sample database, with few test records and show the required output.

A suggestion with my existing tables: a( adesc, ...), and b(besc,...)

adesc
b,a
c,b
d,c
....

bdesc
a b
b c
c d

SELECT a.adesc, b.bdesc
FROM a, b
WHERE (Left(a.adesc,InStr(a.adesc,",")-1)=right(b.bdesc,len(b.bdesc)-instr(b.bdesc," ")))
            AND (Left(b.bdesc,InStr(b.bdesc," ")-1)=right(a.adesc,len(a.adesc)-instr(a.adesc,",")))

Open in new window

adesc      bdesc
b,a         a b
c,b         b c
d,c         c d
,,,,,
You may add other required fields.

I go with
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.