T
Tracy
the table I created won't record a calculated field after the 200th record.
Can anybody tell me how to fix this?
Can anybody tell me how to fix this?
the table I created won't record a calculated field after the 200th record.
Can anybody tell me how to fix this?
I have a form set up that takes the students tuition for the year and
separates it into billing for the semester. The formula is in the form.
After the 200th record the table stopped filling in the price per semester.
Can you help me with this? I would be greatly appreciatative.
Tracy
- Show quoted text -
Matt said:Tables shouldnt really have calculated fields ... keep the basic data
in the tables and use queries to calculate on these fields.
As to why it is stopping you after 200 records is a little weird.
Could you provide some more details on what you are doing?
Matt said:Tables shouldnt really have calculated fields ... keep the basic data
in the tables and use queries to calculate on these fields.
As to why it is stopping you after 200 records is a little weird.
Could you provide some more details on what you are doing?
record. The price is showing on the form but it isn't populating the
table
after the 200th record.
I'm sorry, this is new to me. My table is set up with the full tution cost
in colume A, first semester cost in colume B and second semester cost in
colume C. My formula is in the form and is as follows: [TUITION]/2+50 and
[TUITION]/2-50. I hope this helps you to help me.
John W. Vinson said:I'm sorry, this is new to me. My table is set up with the full tution cost
in colume A, first semester cost in colume B and second semester cost in
colume C. My formula is in the form and is as follows: [TUITION]/2+50 and
[TUITION]/2-50. I hope this helps you to help me.
You're thinking in spreadsheet terms.
Will you never have a student who attends only one semester?
Will Column A always be the sum of columns B and C? If so, it SHOULD NOT EXIST
in your table, it should be calculated on demand!
I'd suggest a quite different design: a one to many relationship from a table
of Students to a table of TuitionCosts:
Students
StudentID <primary key>
LastName
FirstName
<other biographical data>
TuitionCosts
StudentID <part of primary key, link to Students>
Semester <rest of Primary Key, maybe a date field, maybe text such as
"Spring 2007">
Cost
<maybe other fields, e.g. reason for discount or waiver of fees>
You'ld put two records in TuitionCosts for the two semesters, and calculate
your expressions dynamically on a Form by setting the control source of an
unbound textbox to your expression.
John W. Vinson [MVP]
Tracy said:Thank you for the information. I am going to try it and see what happens. I
will let you know.
Tracy
John W. Vinson said:I'm sorry, this is new to me. My table is set up with the full tution cost
in colume A, first semester cost in colume B and second semester cost in
colume C. My formula is in the form and is as follows: [TUITION]/2+50 and
[TUITION]/2-50. I hope this helps you to help me.
You're thinking in spreadsheet terms.
Will you never have a student who attends only one semester?
Will Column A always be the sum of columns B and C? If so, it SHOULD NOT EXIST
in your table, it should be calculated on demand!
I'd suggest a quite different design: a one to many relationship from a table
of Students to a table of TuitionCosts:
Students
StudentID <primary key>
LastName
FirstName
<other biographical data>
TuitionCosts
StudentID <part of primary key, link to Students>
Semester <rest of Primary Key, maybe a date field, maybe text such as
"Spring 2007">
Cost
<maybe other fields, e.g. reason for discount or waiver of fees>
You'ld put two records in TuitionCosts for the two semesters, and calculate
your expressions dynamically on a Form by setting the control source of an
unbound textbox to your expression.
John W. Vinson [MVP]