correct. it stays blank. but I didn't update the field or anything after I got rid of my linked fields on the table. I'll try that.
correct. it stays blank. but I didn't update the field or anything after I got rid of my linked fields on the table. I'll try that.
Access tries very hard *not* to Dirty a record and force you to then deal with the record that now needs to be saved or cleared.
AH HAH!!!! That was it.. sort of
So went back and looked at my query that the subform was based on. and I had my three linked tables in the query and all of the fields from all the tables. So I deleted everything and got back to basics. Just the subtable (as it were) and those fields then I went to my subform and made sure everything linked up. It now autopopulates!!! Yay! You have been very helpful. I need a class in advanced Access. *sigh* thanks
Excellent! Are you ready to use the Thread Tools and mark this thread as Solved?
OK, so now. What do I do to make sure I don't create records with no data. So, for example say I put a date in (i.e. dirty the record) and then realize this isn't the employee I meant to be entering a record for. If I hit the Esc key I am still left with a new record containing the EmpID. I suppose I could do a button to "Cancel" which would delete the new record. Is that the right way to handle that?
Two escapes should do it and it is not necessary to delete the record yet since it has not been created until you move the focus off of the record or SubForm. If you need an *oops* button then you might as well save the record and then delete it since pressing the OopsButton would probably cause the save.
Awesome!!! Thanks a bunch!