Control Source on a Text Box

[Mark Lees]

I've created some fields that calculate future dates. The way they are
set up they do not save to a table. This is the expression I used
(=DateSerial(Ye ar([IFSPOrginal]),Month([IFSPOrginal])+6,Day([IFSPOrginal]).
I placed it in the Control Source property. I want to save them to a
table so I can use them on a report.

So the 2 questions are:

1. How do you use a calculated field that doesn't save to a table in
a report?

2. If you have to save it to a table to use it in a report, where do
I put the expression so it does the calculation other than control
source property?

Thanks
Mark

[fredg]

On 26 Feb 2004 11:04:52 -0800, Mark Lees wrote:

I've created some fields that calculate future dates. The way they are
set up they do not save to a table. This is the expression I used
(=DateSerial(Ye ar([IFSPOrginal]),Month([IFSPOrginal])+6,Day([IFSPOrginal]).
I placed it in the Control Source property. I want to save them to a
table so I can use them on a report.

So the 2 questions are:

1. How do you use a calculated field that doesn't save to a table in
a report?

2. If you have to save it to a table to use it in a report, where do
I put the expression so it does the calculation other than control
source property?

Thanks
Mark

Regarding #1, above:
You don't save the calculated field to a table, you repeat the same
calculation in the report.
As long as your table contains the data in the fields used in the
calculations, that's all you need.

Regarding #2, above:
See my response to #1.
--
Fred
Please only reply to this newsgroup.
I do not reply to personal email.

[Bas Cost Budde]

Mark Lees wrote:

I've created some fields that calculate future dates. The way they are
set up they do not save to a table. This is the expression I used
(=DateSerial(Ye ar([IFSPOrginal]),Month([IFSPOrginal])+6,Day([IFSPOrginal]).
I placed it in the Control Source property. I want to save them to a table so I can use them on a report.
You may assume that a report can be built on a table only. That is not
the case: you can use a query as source for the report. That happens to
be frequent use.
So the 2 questions are:

1. How do you use a calculated field that doesn't save to a table in
a report?
In a query. Or, immediately on the report: ou can set the controlsource
of report fields just as you set them in forms.
2. If you have to save it to a table to use it in a report, where do
I put the expression so it does the calculation other than control
source property?

It is so much advised against, that I couldn't even provide a technical
answer. Just don't store the calculated value.
--
Bas Cost Budde
http://www.heuveltop.org/BasCB
but the domain is nl

[MGFoster]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

First off, you can use the DateAdd() function to add 6 months to the
date value IFSPOriginal:

DateAdd("m", 6, IFSPOriginal)

If the date IFSPOriginal is saved to the table you can use the same
function in the report. Use an unbound TextBox and set its
ControlSource to this:

=DateAdd("m", 6, [IFSPOriginal])
MGFoster:::mgf0 0 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQD5KIoechKq OuFEgEQJboQCgyH xsDYcCz9HnP2q6v zEm30pnwF4An27A
fhqZr+nTo3uqW7Y 56SvTL5XF
=LrYG
-----END PGP SIGNATURE-----
Mark Lees wrote:

I've created some fields that calculate future dates. The way they are
set up they do not save to a table. This is the expression I used
(=DateSerial(Ye ar([IFSPOrginal]),Month([IFSPOrginal])+6,Day([IFSPOrginal]).
I placed it in the Control Source property. I want to save them to a
table so I can use them on a report.

So the 2 questions are:

1. How do you use a calculated field that doesn't save to a table in
a report?

2. If you have to save it to a table to use it in a report, where do
I put the expression so it does the calculation other than control
source property?

[Mark Lees]

Thanks!

[Mark Lees]

Thanks!

[Mark Lees]

MGFoster:

Thanks for the help. However if I set it up with the DateAdd function
it asks me for a parameter value and bases the results from the
parameter value and not the one stored in IFSPOrignal.

MGFoster <[e-mail] > wrote in message news:<PS******* **********@news read2.news.pas. earthlink.net>. ..

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

First off, you can use the DateAdd() function to add 6 months to the
date value IFSPOriginal:

DateAdd("m", 6, IFSPOriginal)

If the date IFSPOriginal is saved to the table you can use the same
function in the report. Use an unbound TextBox and set its
ControlSource to this:

=DateAdd("m", 6, [IFSPOriginal])
MGFoster:::mgf0 0 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQD5KIoechKq OuFEgEQJboQCgyH xsDYcCz9HnP2q6v zEm30pnwF4An27A
fhqZr+nTo3uqW7Y 56SvTL5XF
=LrYG
-----END PGP SIGNATURE-----
Mark Lees wrote:

I've created some fields that calculate future dates. The way they are
set up they do not save to a table. This is the expression I used
(=DateSerial(Ye ar([IFSPOrginal]),Month([IFSPOrginal])+6,Day([IFSPOrginal]).
I placed it in the Control Source property. I want to save them to a
table so I can use them on a report.

So the 2 questions are:

1. How do you use a calculated field that doesn't save to a table in
a report?

2. If you have to save it to a table to use it in a report, where do
I put the expression so it does the calculation other than control
source property?