Hi everybody,

Is there a way I can read an Outlook or Outlook Express address book (.wab)
into access to be able to drop email addresses into a filed?

No problem reading .csv file generated by the address book but that relies
on somebody updating the .csv file
continuously *AND* I don't really have a unique key I to avoid duplicated
records if I import the .csv file into a table more then once.


Any suggestions?

TIA

Jacob

Ooops,

I just saw that someone else asked a similar question. Do I take the answer
to my question as "you can't do it" ?

Regards/JK

"JK" <(E-Mail Removed)> wrote in message
news:eh$(E-Mail Removed)...
> Hi everybody,
>
> Is there a way I can read an Outlook or Outlook Express address book
> (.wab) into access to be able to drop email addresses into a filed?
>
> No problem reading .csv file generated by the address book but that relies
> on somebody updating the .csv file
> continuously *AND* I don't really have a unique key I to avoid duplicated
> records if I import the .csv file into a table more then once.
>
>
> Any suggestions?
>
> TIA
>
> Jacob
>
>

JK wrote:
> Ooops,
>
> I just saw that someone else asked a similar question. Do I take the
> answer to my question as "you can't do it" ?
>
> Regards/JK
>

Well you can't do it directly.

--
Joseph Meehan

Dia duit

Thanks Joseph,
Looks like I will have to use .CSV file and find some way to avoid or at
least minimize duplications.

Regards
Jacob



"Joseph Meehan" <(E-Mail Removed)> wrote in message
news:0SnZg.16671$(E-Mail Removed)...
> JK wrote:
>> Ooops,
>>
>> I just saw that someone else asked a similar question. Do I take the
>> answer to my question as "you can't do it" ?
>>
>> Regards/JK
>>
>
> Well you can't do it directly.
>
> --
> Joseph Meehan
>
> Dia duit
>

JK wrote:
> Thanks Joseph,
> Looks like I will have to use .CSV file and find some way to avoid or
> at least minimize duplications.

If you have a unique field you can eliminate duplicate by making that a
key field without duplicates allowed.
>
> Regards
> Jacob
>
>
>
> "Joseph Meehan" <(E-Mail Removed)> wrote in message
> news:0SnZg.16671$(E-Mail Removed)...
>> JK wrote:
>>> Ooops,
>>>
>>> I just saw that someone else asked a similar question. Do I take the
>>> answer to my question as "you can't do it" ?
>>>
>>> Regards/JK
>>>
>>
>> Well you can't do it directly.
>>
>> --
>> Joseph Meehan
>>
>> Dia duit



--
Joseph Meehan

Dia duit

On Wed, 18 Oct 2006 21:14:32 +1000, "JK" <(E-Mail Removed)> wrote:

>Thanks Joseph,
>Looks like I will have to use .CSV file and find some way to avoid or at
>least minimize duplications.
>
>Regards
>Jacob
>
>
>
>"Joseph Meehan" <(E-Mail Removed)> wrote in message
>news:0SnZg.16671$(E-Mail Removed)...
>> JK wrote:
>>> Ooops,
>>>
>>> I just saw that someone else asked a similar question. Do I take the
>>> answer to my question as "you can't do it" ?
>>>
>>> Regards/JK
>>>
>>
>> Well you can't do it directly.
>>
>> --
>> Joseph Meehan
>>
>> Dia duit
>>
>

A dbf (dBase III or IV) might work better for you.
Charlie Hoffpauir
http://freepages.genealogy.rootsweb.com/~charlieh/

Joseph,

I basically need to bring in First Name, Middle Name, Last Name, Name and
e-mail address. None of these can be a unique field by itself. Sure, I have
an Email_ID as key, but that does not prevents importing the same person
again.

I will have to test on all five fields and eliminate exact match on all 5,
But if the user change an existing entry in the address book (typos,
spelling
, e-mail address etc.) that record will come in as a new record. Nothing
much I can do about it but I don't expect that to be a major problem, people
usually add or delete records in their address book or changing e-mail
addresses - I shall have to let it go and refine the process if/when it will
cause problems (I don't think so.

Another approach is the KISS principle (Keep It Simple, Stupid :-) say "no
can
do" and let the users enter the e-mail addresses manually - they know the
addressees better than I do.

Regards/JK




"Joseph Meehan" <(E-Mail Removed)> wrote in message
news:5eqZg.16681$(E-Mail Removed)...
> JK wrote:
>> Thanks Joseph,
>> Looks like I will have to use .CSV file and find some way to avoid or
>> at least minimize duplications.
>
> If you have a unique field you can eliminate duplicate by making that a
> key field without duplicates allowed.
>>
>> Regards
>> Jacob
>>
>>
>>
>> "Joseph Meehan" <(E-Mail Removed)> wrote in message
>> news:0SnZg.16671$(E-Mail Removed)...
>>> JK wrote:
>>>> Ooops,
>>>>
>>>> I just saw that someone else asked a similar question. Do I take the
>>>> answer to my question as "you can't do it" ?
>>>>
>>>> Regards/JK
>>>>
>>>
>>> Well you can't do it directly.
>>>
>>> --
>>> Joseph Meehan
>>>
>>> Dia duit
>
>
>
> --
> Joseph Meehan
>
> Dia duit
>

Joseph,

I basically need to bring in First Name, Middle Name, Last Name, Name and
e-mail address. None of thses can be a unique field by itself. Sure, I have
an Email_ID as key in the table, but that does not prevents importing the
same person again.

I will have to test on all five fields and eliminate exact match on all 5,
But if the user change an exsiting entry in the addres book (typos, spelling
, e-mail address etc.) that record will come in as a new record. Nothing
much I can do about it but I don't expect that to be a major problem, people
usually add or delete records in their addrees book or changing e-mail
addresses - I shall have to let it go and refine the process if/when it will
cause problems (I don't think so.

Another approach is the KISS princple (Keep It Simle, Stupid :-) say "no can
do" and let the users enter the e-mail addresses manually -t hey know the
addressees beter than I do.

Regards/JK




"Joseph Meehan" <(E-Mail Removed)> wrote in message
news:5eqZg.16681$(E-Mail Removed)...
> JK wrote:
>> Thanks Joseph,
>> Looks like I will have to use .CSV file and find some way to avoid or
>> at least minimize duplications.
>
> If you have a unique field you can eliminate duplicate by making that a
> key field without duplicates allowed.
>>
>> Regards
>> Jacob
>>
>>
>>
>> "Joseph Meehan" <(E-Mail Removed)> wrote in message
>> news:0SnZg.16671$(E-Mail Removed)...
>>> JK wrote:
>>>> Ooops,
>>>>
>>>> I just saw that someone else asked a similar question. Do I take the
>>>> answer to my question as "you can't do it" ?
>>>>
>>>> Regards/JK
>>>>
>>>
>>> Well you can't do it directly.
>>>
>>> --
>>> Joseph Meehan
>>>
>>> Dia duit
>
>
>
> --
> Joseph Meehan
>
> Dia duit
>

Hmmm, last time I used dBase III was about 13 year ago the good aold days of
DOS :-o

"Charlie Hoffpauir" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Wed, 18 Oct 2006 21:14:32 +1000, "JK" <(E-Mail Removed)> wrote:
>
>>Thanks Joseph,
>>Looks like I will have to use .CSV file and find some way to avoid or at
>>least minimize duplications.
>>
>>Regards
>>Jacob
>>
>>
>>
>>"Joseph Meehan" <(E-Mail Removed)> wrote in message
>>news:0SnZg.16671$(E-Mail Removed)...
>>> JK wrote:
>>>> Ooops,
>>>>
>>>> I just saw that someone else asked a similar question. Do I take the
>>>> answer to my question as "you can't do it" ?
>>>>
>>>> Regards/JK
>>>>
>>>
>>> Well you can't do it directly.
>>>
>>> --
>>> Joseph Meehan
>>>
>>> Dia duit
>>>
>>
>
> A dbf (dBase III or IV) might work better for you.
> Charlie Hoffpauir
> http://freepages.genealogy.rootsweb.com/~charlieh/

On Thu, 19 Oct 2006 02:17:24 +1000, "JK" <(E-Mail Removed)> wrote:

>Hmmm, last time I used dBase III was about 13 year ago the good aold days of
>DOS :-o
>
>"Charlie Hoffpauir" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed)...
>> On Wed, 18 Oct 2006 21:14:32 +1000, "JK" <(E-Mail Removed)> wrote:
>>
>>>Thanks Joseph,
>>>Looks like I will have to use .CSV file and find some way to avoid or at
>>>least minimize duplications.
>>>
>>>Regards
>>>Jacob
>>>
>>>
>>>
>>>"Joseph Meehan" <(E-Mail Removed)> wrote in message
>>>news:0SnZg.16671$(E-Mail Removed)...
>>>> JK wrote:
>>>>> Ooops,
>>>>>
>>>>> I just saw that someone else asked a similar question. Do I take the
>>>>> answer to my question as "you can't do it" ?
>>>>>
>>>>> Regards/JK
>>>>>
>>>>
>>>> Well you can't do it directly.
>>>>
>>>> --
>>>> Joseph Meehan
>>>>
>>>> Dia duit
>>>>
>>>
>>
>> A dbf (dBase III or IV) might work better for you.
>> Charlie Hoffpauir
>> http://freepages.genealogy.rootsweb.com/~charlieh/
>

Perhaps I wasn't clear. You don't need to "use" dBase. From Works, you
can save your table as a dbf file. Access will then import the dbf
file. You'll basically have the same table you had in Works.... just
build the Queries and Reports in Access.

Charlie Hoffpauir
http://freepages.genealogy.rootsweb.com/~charlieh/