Hey Richard, Hope you had a great Turkey day and the New Security Seminair is looking great although I have a task at hand and the reason I writing. I have created a Access 2007 DB to help pull work hours and Payroll data together and have used the position number as the link between three tables. Workhours, PayrollData, and Personnel list. The first two are data that is from our mainframe(pay) and a SAP platform(hours)which talk to one another. The personnel list in one in Access so I can know who to pull for the merge of this data and is maintained by our staff. Well this was great until I over looked something I forgot to account for. OPS staff come and go a lot and we just add the new OPS person when the old one leaves and can use the same position number and track both employees with no problem. THe problem I forgot about is when a Fulltime person changes poisiton number and is not leaving and now may have hours and pay data split between two position numbers. What I'm trying to do is maintain only one record for fulltime staff and figure out how to tie both position numbers together with that one record. I could add another record for that person with the new position number but I think somewhere in the training you have I've seen soemthing on this issue and how to solve it. Can you point me to the correct lesson that has this or is there not a example of this type issue. I can email a structure of the tables if that help give a better picture. I'm over looking something I sure as I've not worked in Access this much in a while and with the new version things are not coming to mind as they did in the 2003 version. Which also brings up the question about menus which I like using forms and not the siwtchboard but what is your take on this as the new version is not as user friendly as in the older version. BUt the main thing I'm look for right now is a way to fix this issue before I get to many records in the tables and have to do to major update table to fix these tables. I also use the autonumber field in all tables for a ID field.Basically the personnel table is a one to many records in each of the other tables and the position number is the link to all of them. But like I said I didn't account for a fulltime pesron changing position numbers and now need a solution to my oversite if you can help. This would complete my DB and allow me to put into production but is a set back for me as of now and as I said I believe you have a lesson showing this I just can't put my finger on it. I see the new security lessons are going to be great as I see soemthing I can use it in the next project after this one I'm referring to now. Again Hope you had a great T day and I look forward to hearing back from you on this. Thanks again too for all the great lessons as this has been the greatest investment I have made in learning Access and all the other great lessons you have. I just hope all those I have recomended to use your courses are doing so as they will also be making a great investment in my opinion and look forward to seeing what other great lessons you have coming up. Thanks for all your hard work and may God richly bless you now and in the coming days. May you and your family also have a great Christmas and New Years. Steve C.