MS Access Multiuser - DB Suggestions please

Author

DB Suggestions please

LJG

2006-01-14, 7:23 am

Hi Guys,

Just wondering if anyone can help me with this problem, maybe provide some
suggestions?

12 months ago we started using a field sales contact database for a team of
8 salesmen, this has worked very well the primary key for the contacts is
contactID (autonumber)with notes being notesID (autonumber)

Each of these will have started from 1

The issue I have now is that as it has worked so well we are about to
implement the system internally for the telesales team who will then send
out contacts and appointment information for the sales team to import into
their contacts DB. The internal DB also uses contactID and noteID as the PK
and as these are also (autonumber)

The problem I have is that we would like to pass back data from the field
sales to the internal system for the internal team to keep in touch with
contacts and keep records of all contacts.

The issues I have is

Duplicated contactID's
Duplicated notesID's

As part of the project the aim is to allow internal & field sales to be kept
in touch with all prospects and share notes etc.

Ultimately new contacts will be made via the internal team to send out to
the various sales member, however, we still need to allow the field sales to
create new records and also pass back to internal to update their system

Can anyone suggest any method to make this process work, hopefully this
description will provide a picture of what I am doing and need to ensure we
do not end up with duplicated data

Any suggestions would be most welcome

TIA
Les

Amy Blankenship

2006-01-14, 1:23 pm

How bout specifying one database as the Master database, then add
MasterContactID, MasterNoteID to the "Child" databases, so you can always be
sure you're talking about the same contact when talking "across" databases?

You could also look at replication, but it seems to me that MS has made
replication one of the more unusable features of Access...

HTH;

Amy

"LJG" < lj_girvan@no_spam_ho
tmail.com> wrote in message
news:%23e82zhPGGHA.3916@TK2MSFTNGP10.phx.gbl...
> Hi Guys,
>
> Just wondering if anyone can help me with this problem, maybe provide some
> suggestions?
>
> 12 months ago we started using a field sales contact database for a team
> of 8 salesmen, this has worked very well the primary key for the contacts
> is contactID (autonumber)with notes being notesID (autonumber)
>
> Each of these will have started from 1
>
> The issue I have now is that as it has worked so well we are about to
> implement the system internally for the telesales team who will then send
> out contacts and appointment information for the sales team to import into
> their contacts DB. The internal DB also uses contactID and noteID as the
> PK and as these are also (autonumber)
>
> The problem I have is that we would like to pass back data from the field
> sales to the internal system for the internal team to keep in touch with
> contacts and keep records of all contacts.
>
> The issues I have is
>
> Duplicated contactID's
> Duplicated notesID's
>
> As part of the project the aim is to allow internal & field sales to be
> kept in touch with all prospects and share notes etc.
>
> Ultimately new contacts will be made via the internal team to send out to
> the various sales member, however, we still need to allow the field sales
> to create new records and also pass back to internal to update their
> system
>
> Can anyone suggest any method to make this process work, hopefully this
> description will provide a picture of what I am doing and need to ensure
> we do not end up with duplicated data
>
> Any suggestions would be most welcome
>
> TIA
> Les
>
>

Ian Davies

2006-01-30, 8:25 pm

hi
Change the field size of your autonumber fields in your tables to
Replication ID
This will create a unique value for each record even in different databases
This fieldsize does however use more disc space than the others

Ian

"LJG" < lj_girvan@no_spam_ho
tmail.com> wrote in message
news:%23e82zhPGGHA.3916@TK2MSFTNGP10.phx.gbl...
> Hi Guys,
>
> Just wondering if anyone can help me with this problem, maybe provide some
> suggestions?
>
> 12 months ago we started using a field sales contact database for a team
of
> 8 salesmen, this has worked very well the primary key for the contacts is
> contactID (autonumber)with notes being notesID (autonumber)
>
> Each of these will have started from 1
>
> The issue I have now is that as it has worked so well we are about to
> implement the system internally for the telesales team who will then send
> out contacts and appointment information for the sales team to import into
> their contacts DB. The internal DB also uses contactID and noteID as the
PK
> and as these are also (autonumber)
>
> The problem I have is that we would like to pass back data from the field
> sales to the internal system for the internal team to keep in touch with
> contacts and keep records of all contacts.
>
> The issues I have is
>
> Duplicated contactID's
> Duplicated notesID's
>
> As part of the project the aim is to allow internal & field sales to be
kept
> in touch with all prospects and share notes etc.
>
> Ultimately new contacts will be made via the internal team to send out to
> the various sales member, however, we still need to allow the field sales
to
> create new records and also pass back to internal to update their system
>
> Can anyone suggest any method to make this process work, hopefully this
> description will provide a picture of what I am doing and need to ensure
we
> do not end up with duplicated data
>
> Any suggestions would be most welcome
>
> TIA
> Les
>
>

Sponsored Links