Inactive employees

[Guest]

As employees come and go, I need to remove and add them from the Rep table.
However if I remove a Rep then any sales assigned to that person will become
“fubarâ€. So instead of removing them I know I need to make them inactive (via
a check box). I still need to see all the customers “Sam†sold to, but I
don’t want to see his name as an option in the list on any new sales after he
becomes inactive. How do I setup the form(s) to utilize the Rep table for the
combo box to draw from?

 

[John W. Vinson]

As employees come and go, I need to remove and add them from the Rep table.
However if I remove a Rep then any sales assigned to that person will become
“fubar”. So instead of removing them I know I need to make them inactive (via
a check box). I still need to see all the customers “Sam” sold to, but I
don’t want to see his name as an option in the list on any new sales after he
becomes inactive. How do I setup the form(s) to utilize the Rep table for the
combo box to draw from?

Just add a Yes/No field to the table; I'd name it Active and have it default
to True.

You can base a combo box on a query selecting only active reps. For your
reports, don't use the active criterion so you'll see all the reps, past and
present.

 

[Guest]

Thanks, I assumed I would need to base the combo box on a query, but I hate
to ass-u-me.

I am in the early stages of redesigning our current DB. When done, I plan to
import the customer records, orders etc., however I need to make some data
changes to some of the lookup tables and I worry if this will mess up the
import.

Quick example: the old DB has Sam as rep with ID of 1. In new DB Sam's RepID
is 4. When I import can I make sure that import relationship is based upon
the name (nonduplicate) or must it be on the ID and I have to keep all the
supporting (lookup) tables' data as it is in the old DB?

I wanted to fix a number of lookup tables, for example the tblState has two
Vermonts. (The first designer wasn't overly careful with some things). What
do you recommend?

 

[John W. Vinson]

Thanks, I assumed I would need to base the combo box on a query, but I hate
to ass-u-me.

I am in the early stages of redesigning our current DB. When done, I plan to
import the customer records, orders etc., however I need to make some data
changes to some of the lookup tables and I worry if this will mess up the
import.

Quick example: the old DB has Sam as rep with ID of 1. In new DB Sam's RepID
is 4. When I import can I make sure that import relationship is based upon
the name (nonduplicate) or must it be on the ID and I have to keep all the
supporting (lookup) tables' data as it is in the old DB?

I wanted to fix a number of lookup tables, for example the tblState has two
Vermonts. (The first designer wasn't overly careful with some things). What
do you recommend?

Tedium, concentration, hard work and frustration. <g>

You can import the lookup data and - if need be - use a Query joining on the
text value (if it's unique) to update the numeric foreign key value.

 

[Guest]

Thank you once again, you're one of my favorite helpers!! I also assumed I
should do it that way, but you're right, it can be frustrating ... etc.

Thanks
CAC