> HI all,
>
> I was wondering HOW DBA's handle things like this.
> Here is a scenario, simlpistict but real. Also multipl this by as many as
> you want to understand the potential proble,m
> A few salesman on the road, each with some kind of mobile device. THey are
> not conencted to the company database, but will syncronise when they reach
> the office. This could be hours to days later. Two of the salesman might
> work an area. salesmana aproaches Joe and sels him some stuff. Joe is a new
> client so the Salesmans disconnected app creates adataset, withJoes new
> information, intending to INSERT Joe as a new customer, he also creates new
> invoices with  line items, products etc.
> Next day Salesmanb Aproaches Joe, and sells him some more stuff, but
> according to him Joe is  new customer. exactly sme scenario as above, but he
> Inserts and updates the Company database the next day. SOme of the items
> sold to Joe, have already been orders and invoiced by salesmana.
> SAlesman a then comes in and trys to nsert and update the Company database.
> We now have so many potential problems ranging from duplicate Joes, to
> Duplicate sales to sales not being assigned to the crrect salesman. Hoe does
> one deal with this situation, in the real world, when it comes to
> PrimaryKeys, contrants, making sure of the integraty of the Company data,
> etc etc. THe list goes on.
> One of the many potential things to fix, is the erging of invoice data,
> re-aligning the sales data to the correct salesman etc etc.
>
> This sceario not only happens in the idea of sales, but in a wide variety of
> situations