attach a file
in [General]
|
From: Bob76 on 15 Apr 2010 01:41 I have a table of employees with data such as EmplName, Status, Jobsite, DateHired, PayRate. I would like to link each employee to a form where the Project Manager can write down day to day comments on each employee. I would appreciate any suggestions on how to set this up. Thanks a lot, Bob76
From: PieterLinden via AccessMonster.com on 15 Apr 2010 02:03 Bob76 wrote: >I have a table of employees with data such as EmplName, Status, Jobsite, >DateHired, PayRate. I would like to link each employee to a form where the >Project Manager can write down day to day comments on each employee. I would >appreciate any suggestions on how to set this up. >Thanks a lot, >Bob76 Whoa. You don't link records to forms. You base forms on tables or queries. You could achieve what you want by creating a form based on Employee. Then you could have a subform based on DailyComments and then add a comment for each day. It might be something like this: EmployeeID Long (PK1) CommentDate date (PK2) Comment (Memo) If you declare a relationship between Employee and EmployeeComments, this should be almost automatic. -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/Forums.aspx/access/201004/1
From: John W. Vinson on 15 Apr 2010 02:09 On Wed, 14 Apr 2010 22:41:01 -0700, Bob76 <Bob76(a)discussions.microsoft.com> wrote: >I have a table of employees with data such as EmplName, Status, Jobsite, >DateHired, PayRate. I would like to link each employee to a form where the >Project Manager can write down day to day comments on each employee. I would >appreciate any suggestions on how to set this up. >Thanks a lot, >Bob76 You really should have a unique EmployeeID field: names are NOT unique. I once worked with Dr. Lawrence David Wise, Ph.D. and his colleague, Dr. Lawrence David Wise, Ph.D. Given that... I'd suggest a table with (perhaps) four fields - EmployeeID (a link to the employee table); CommenterID (another link to the employee table, to select the person making the comment); CommentDateTime, a Date/Time field with a default value of =Now() to automatically timestamp the comment; and a Memo field Comment. You could display this table in a Subform on the employee form, with EmployeeID as the master/child link field and a combo box to select the ID of the person making the comment. -- John W. Vinson [MVP]
From: Bob76 on 15 Apr 2010 21:57 Sorry, I do have Empl. No. as my primary key, forgot to put that down in my post. Thanks for your suggestions.. I will try out your idea and also that of Pieter. I will have to read more about subforms as I'm not familiar with this yet.. I'm fairly new to Access. "John W. Vinson" wrote: > On Wed, 14 Apr 2010 22:41:01 -0700, Bob76 <Bob76(a)discussions.microsoft.com> > wrote: > > >I have a table of employees with data such as EmplName, Status, Jobsite, > >DateHired, PayRate. I would like to link each employee to a form where the > >Project Manager can write down day to day comments on each employee. I would > >appreciate any suggestions on how to set this up. > >Thanks a lot, > >Bob76 > > You really should have a unique EmployeeID field: names are NOT unique. I once > worked with Dr. Lawrence David Wise, Ph.D. and his colleague, Dr. Lawrence > David Wise, Ph.D. > > Given that... I'd suggest a table with (perhaps) four fields - EmployeeID (a > link to the employee table); CommenterID (another link to the employee table, > to select the person making the comment); CommentDateTime, a Date/Time field > with a default value of =Now() to automatically timestamp the comment; and a > Memo field Comment. You could display this table in a Subform on the employee > form, with EmployeeID as the master/child link field and a combo box to select > the ID of the person making the comment. > -- > > John W. Vinson [MVP] > . >
|
Pages: 1 Prev: microsoft.public.access.conversion Next: Color Values in VBA |