Help with Database Solution

[Stephen]

I volunteer for a non-for profit group and they have alot of names in a
multiple databases. the problem is that some people are in multiple
databases. and if they send out a mailing from multiple databases some
people get 2 and 3 of the same thing. my idea was to either make or find a
program that has everyone is 1 database and then make the people part of
multiple groups. (ex: bill is part of group a and b and im doing a mailing
from both group i only want 1 piece of mail to go to him).

It can be a separate program or with access. that use access now but i cant
figure out how to make my idea work.

any question please ask.
tia
Stephen

[ManningFan]

Re: Help with Database Solution

Try switching to Act! software. It's built for this type of situation.

Short of that, you're going to have to code it from the ground up.
Design it on paper first and think through the way the tables need to
join to get your data to work properly. It may take some time, but
proper database layouts will save you a mountain of headaches in the
future.

Stephen wrote:

I volunteer for a non-for profit group and they have alot of names in a
multiple databases. the problem is that some people are in multiple
databases. and if they send out a mailing from multiple databases some
people get 2 and 3 of the same thing. my idea was to either make or find a
program that has everyone is 1 database and then make the people part of
multiple groups. (ex: bill is part of group a and b and im doing a mailing
from both group i only want 1 piece of mail to go to him).
>
It can be a separate program or with access. that use access now but i cant
figure out how to make my idea work.
>
any question please ask.
tia
Stephen

[Ted]

Re: Help with Database Solution


ManningFan wrote:

Try switching to Act! software. It's built for this type of situation.
>

Act! is an impressive peice of software, but I didn't much like writing
code to interface with it. I encountered a number of bugs in the SDK
for it (but that was long enough ago that the bugs I encountered should
be long fixed).

OTOH, isn't SQL Server Integration Services also designed for this kind
of problem? It was recommended to me, and I have only begun to study
it, but as I recall from what I read about it, I would think it could
be useful here.

Cheers,

Ted