Re: DB2, MsSQL, and MS Access, How to maintain 3 data sources
- From: David Richards <david.richards@xxxxxxxxxxx>
- Date: Thu, 14 Jul 2005 23:54:55 -0700
Hi, there,
Thanks for the response.
The information stored will be customer names, and addresses. Each
customer will have an area code, and it is this code that will be used
to split the data over the 20 laptops. This means that no two salesmen
will ever have the same customers in there database. The salesmen will
have the ability to create quotes, and call logs for a specified
customer. This data will obviously be stored in separate tables to the
customer?s names and addresses.
A quick example:
The salesmen selects a customer with a unique ID of 103, He then create
a quote for this customer causing a record to be created in the quote
header table. The customer ID of 103 is assigned to FK_customer ID in
the quotes header table.
Salesmen will be allowed to add new customers to there database, and
create quotes for them. Imagine two salesmen add two separate and
different customers to there database and both copies of MS Access
assign a customer ID of 107. When both salesmen synchronize then will be
a duplicate customer ID. I could have the SQL server ignore there
customer ID and create a new one, but what happens to all the quote
records?
This is really the problem, how can I work it so that I can have both
the SQL server, and all copies of the ms access databases generate
unique customer ID?s? As they will all be capable of creating new
customer records.
Thanks
Dave
*** Sent via Developersdex http://www.developersdex.com ***
.
- Follow-Ups:
- References:
- Prev by Date: Re: Advanced filter method
- Next by Date: Re: DB2, MsSQL, and MS Access, How to maintain 3 data sources
- Previous by thread: Re: DB2, MsSQL, and MS Access, How to maintain 3 data sources
- Next by thread: Re: DB2, MsSQL, and MS Access, How to maintain 3 data sources
- Index(es):
Relevant Pages
|
Loading