Advertisement
| Hall of Fame |
|
[x]
Posted via EE Mobile
|
||
Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
||
| Question |
|
[x]
Attachment Details
|
||
|
[x]
The Solution Rating System
|
||
With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.
Your Input Matters If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
||
1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: |
CustID AdddressCreate PhoneCreate FN LN ========================================================== 09136713 2005-04-30 22:55 2005-04-30 22:24 Adam Foo 09136713 2005-05-30 22:55 2005-07-07 10:54 Adam Foo 08811811 2005-06-25 02:34 2005-06-25 02:34 Bill Foo 08811811 2005-07-25 02:34 2005-04-30 22:34 Bill Foo But what I would *like* returned is this: CustID AdddressCreate PhoneCreate FN LN ========================================================== 09136713 2005-05-30 22:55 2005-07-07 10:54 Adam Foo 08811811 2005-07-25 02:34 2005-04-30 22:34 Bill Foo Notice that the records are now unique relative to CustID, and that the records with older AddressCreate dates were eliminated. Since the query joines Member, Address and Phone tables, I need the summary record to contain the latest address AND the latest phone (based on each table's dtstamp column)--and to have unique CustIDs. |