Lifeseeker
Registered User.
- Local time
- Today, 07:54
- Joined
- Mar 18, 2011
- Messages
- 273
Hi,
So I will have an access 2003 form built as the front-end for data entry. The backend links to the SQL server.
With this kind of setup, is it possible to still create derived or calculated fields in the form?
The field very much acts as the decision support, and its value will become "yes" if some other fields value meet certain criteria. My intention is to be able to store this calculated or derived field in the table rather than in the query so that it's easier for people to run queries and stuff. (they can just select the decision support field without using formula to first extract all the "yes" records)
So my question is.....will I need to write the rule for the calculated/derived field in the Access front-end or I do so in the backend?
Any comment/thought much appreciated.
So I will have an access 2003 form built as the front-end for data entry. The backend links to the SQL server.
With this kind of setup, is it possible to still create derived or calculated fields in the form?
The field very much acts as the decision support, and its value will become "yes" if some other fields value meet certain criteria. My intention is to be able to store this calculated or derived field in the table rather than in the query so that it's easier for people to run queries and stuff. (they can just select the decision support field without using formula to first extract all the "yes" records)
So my question is.....will I need to write the rule for the calculated/derived field in the Access front-end or I do so in the backend?
Any comment/thought much appreciated.
