Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. alpinegroove

    After Update Logic - Query or VBA?

    Andrzejek, I am sorry I wasn't clearer in the first place.
  2. alpinegroove

    After Update Logic - Query or VBA?

    Yes, the error was my fault. ProjectIDFK is numeric. That was the problem. EmployeeCar is a yes/no field. I am no longer getting the error now that I fixed that. Why are you trying to stay away from my final objective? The database has certain limitations. It was not fully normalized in the...
  3. alpinegroove

    After Update Logic - Query or VBA?

    does produce" should have been "does not produce"
  4. alpinegroove

    After Update Logic - Query or VBA?

    The type conversion failure error was my fault. Forget that. But that query does produce the result I anticipated.
  5. alpinegroove

    After Update Logic - Query or VBA?

    Sorry I messed up the field names; it should have been: UPDATE tblProjects INNER JOIN tblProjectPeopleRoles ON tblProjects.ProjectID = tblProjectPeopleRoles.ProjectIDFK SET tblProjects.EmployeeCar = IIf([RoleIDFK]="3","-1","0");
  6. alpinegroove

    After Update Logic - Query or VBA?

    Thanks, dhookom. How is it the same information. I am trying to say: if Role X is associated with a record in the junction table, put a different value in a different table, different field.
  7. alpinegroove

    After Update Logic - Query or VBA?

    I came up with this but am getting a type conversion error failure: UPDATE tblProjects INNER JOIN tblProjectPeopleRoles ON tblProjects.ProjectID = tblProjectPeopleRoles.ProjectIDFK SET tblProjects.ProjectHasDriver = IIf([RoleIDFK]="3","-1","0"); ProjectHasDriver is a yes/no field. This might...
  8. alpinegroove

    After Update Logic - Query or VBA?

    Sorry, I missed that in your previous message. EmployeeCar is actually a field in tblProjects so it is not linked to a specific person.
  9. alpinegroove

    After Update Logic - Query or VBA?

    There was no typo. That reference is the in the criteria. It is only use to establish the match, and the code that I posted does update the field to "-1" when the Role=3. My people can have different roles in different projects, even different roles in the same project. I have a junction...
  10. alpinegroove

    After Update Logic - Query or VBA?

    I am a beginner and by no means claim to have a thorough understanding of any of this, but this is how I think this works. If I understand this correctly, yes, if the EmployeeID currently showing in frmCourseInfo is 5, then it would be the same as WHERE EmployeeID = 5. Referring to the form...
  11. alpinegroove

    After Update Logic - Query or VBA?

    1. Why shouldn't it work, and if it shouldn't why does it work? It does update the field with "-1" when the role is 3. 2. How do I handle the other part, when it Role 3 is removed or changed? Thanks
  12. alpinegroove

    After Update Logic - Query or VBA?

    I am having trouble figuring out how to accomplish the following: I have a form linked to tblProjects and subform linked to the junction table tblProjectEmployeeRole. There is an After Update event on the subform: If Me.fkRoleID = 3 Then DoCmd.RunSQL "UPDATE tblEmployees SET EmloyeeCar = '-1'...
  13. alpinegroove

    Help with Many to Many Relationships

    Hello, I am a novice and am trying to develop a database for managing course and instructor information. I have courses, instructors, TAs, and readers. Each course can have more than one instructor, TA, or reader (for example, 1 instructor, 2 TAs, 1 reader or 2 instructors, 1 TA, and 2 readers...

Part and Inventory Search

Back
Top