E
Ernie
I would recommend John's solution, the current salesrep
for a customer can then be found by checking his/her most
recent order. You could generate a blank order for a new
customer just to assign the rep.
The advantage here would be storing the salesrep exactly
once per order and you won't have to change it in two
places if another rep takes over (or assists) that
customer.
solutions for the problem and cannot decide on one or the
other. I have waffled back and for and tried to create
prototypes of each and experiment with them but I still
cannot come to a consensus. Other than someoneâ?Ts
experience I believe the only way I will be able to decide
is to attempt both ideas, and I donâ?Tt think management
will approve that!
add a table for Sales Reps. Each Customer can have one or
many Sales Reps. Each Order must have one Sales Rep.
to do it, but since this will involve almost every part of
the database being changed I am wary of jumping into it. I
am investigating the users needs more to better understand
the problem, but what are the advantages to this approach
and what are the disadvantages to this approach.
relathionship each with tblSalesReps and tblOrders. Then
tblSalesReps will have a one to many relationship with
tblOrders. It creates a circle of tables. It just seems
wrong. Has anybody ever tried an approach similar to this?
Is this a standard approach or is a crackpot idea to save
me work. What are the advantages to this approach and what
are the disadvantages to this approach? Am I going to
paint myself into a corner?
will help me along! Thank you
for a customer can then be found by checking his/her most
recent order. You could generate a blank order for a new
customer just to assign the rep.
The advantage here would be storing the salesrep exactly
once per order and you won't have to change it in two
places if another rep takes over (or assists) that
customer.
some functionality to our database but I have two
solutions for the problem and cannot decide on one or the
other. I have waffled back and for and tried to create
prototypes of each and experiment with them but I still
cannot come to a consensus. Other than someoneâ?Ts
experience I believe the only way I will be able to decide
is to attempt both ideas, and I donâ?Tt think management
will approve that!
Each customer can have many or none orders. Now we want to
add a table for Sales Reps. Each Customer can have one or
many Sales Reps. Each Order must have one Sales Rep.
and tblOrders, tblSalesReps. I know this is the right way
to do it, but since this will involve almost every part of
the database being changed I am wary of jumping into it. I
am investigating the users needs more to better understand
the problem, but what are the advantages to this approach
and what are the disadvantages to this approach.
idea. I will have tblCustomers having a one to many
relathionship each with tblSalesReps and tblOrders. Then
tblSalesReps will have a one to many relationship with
tblOrders. It creates a circle of tables. It just seems
wrong. Has anybody ever tried an approach similar to this?
Is this a standard approach or is a crackpot idea to save
me work. What are the advantages to this approach and what
are the disadvantages to this approach? Am I going to
paint myself into a corner?
the relationships I can email you. Any advice or comments
will help me along! Thank you