Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / January 2006

Tip: Looking for answers? Try searching our database.

DB Suggestions please

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
LJG - 14 Jan 2006 10:51 GMT
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 - 14 Jan 2006 18:56 GMT
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

> Hi Guys,
>
[quoted text clipped - 38 lines]
> TIA
> Les
Ian Davies - 30 Jan 2006 22:43 GMT
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

> Hi Guys,
>
[quoted text clipped - 37 lines]
> TIA
> Les
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.