First, when posting a procedure, please include the entire procedure (from
The easiest way to do this is to have the SQL statement look for the person in question. But, before you start aiming at random possibilities, think about 1) what we have done with some of your other code when dealing with your employees in trying to streamline your code (Hint: use a function which receives an employee ID....) and 2) what similarities and what differences there would be which such a design. Plan it out, then design the procedure.
No--this is not an "answer", but it is guiding you to a solution, based upon principles we have already covered.
Private Sub all the way to End Sub). This allows us to see everything that is going on (even though it looks like we have mostly everything.The easiest way to do this is to have the SQL statement look for the person in question. But, before you start aiming at random possibilities, think about 1) what we have done with some of your other code when dealing with your employees in trying to streamline your code (Hint: use a function which receives an employee ID....) and 2) what similarities and what differences there would be which such a design. Plan it out, then design the procedure.
No--this is not an "answer", but it is guiding you to a solution, based upon principles we have already covered.
Comment