BeckhamTX Posted April 27, 2005 Posted April 27, 2005 I have a db with several tables, two of which are involved in my problem: the Student and School tables. The school table has fields counselorFirstName and counselorLastName and address among others. The student table has fields: address, city, state, postcode, and then a calculated field named MailingAddress. The calculation for the Mailing Address field uses an if statement: If (address ≠ ""; address; "c/o: " & School:counselorFirstName & School:CounselorLastName & School:Address) --Basically, if the student does not have an address in the db, the MailingAddress field should show c/o Counselor at the school address. My problem is that when the counselor name is updated in the school table, the MailingAddress in the student table does not update EVENTHOUGH "Do not replace exisiting value for field" is UNCHECKED. It does update fine if the student does have an address and the address field is changed, then the new address does show up in the MailingAddress field, So....its not updating when the related field (counselor name) is changed. Doesnt unchecking the "Do not replace exisiting value for field" checkbox apply to related fields used in the calculation as well as fields in the same table?
comment Posted April 27, 2005 Posted April 27, 2005 Try making Mailing Address a calculation (not auto-enter) field (result is text) = Case ( IsEmpty ( address ) ; "c/o: " &
BeckhamTX Posted April 28, 2005 Author Posted April 28, 2005 THANK YOU! That worked great....Just what I needed. Do you know why it wouldnt work the way I had it? Ive never had any problems before with that method (but maybe it is an issue of using a related field and Ive just always used it for fields in the same table...) I was just curious to learn the "why" from this mistake. thankx
comment Posted April 28, 2005 Posted April 28, 2005 maybe it is an issue of using a related field Yes, it is. You will notice that a calculation that relies on a related field is automatically unstored. An auto-enter text field cannot be unstored. When you change the value of the related field, the auto-enter field is "not there" to notice the change, so to speak.
Recommended Posts
This topic is 7218 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now