Saving An Expression

J

Joel

I have a query that calculates 2 dates together and i have it showing up on a
form.
How do I save the calculated value into a table?
 
J

Joel

Thank You for your help.

Ok here it is:

I have a form that users enter the date of the inspection in a
textbox[InspectionDate] then they use a combobox ([InspectionFreq]
3m,6m,y1,ect..) to select one of those options.
Now I have a query that calculates the [InspectionDate]+[InspectionFreq]
into an expression [NextInspdate].
This shows up on the form to let them know when the next inspection is.
I need the value of [NextInspDate] to be stored in the table ([MainUnitData]
its the record source of this form).
 
L

Lynn Trapp

That doesn't look like a case where you are keeping the historical value of
a field that might otherwise change. As long as [InspectionDate] and
[InspectionFreq] remain constant for a given record, then you can always
calculate the next inspection date when you need it. Unless I'm missing
something, I see no reason for the MainUnitData needing the value of the
next inspection date. Perhaps if you would post your table structures, i
could see this better.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html



Joel said:
Thank You for your help.

Ok here it is:

I have a form that users enter the date of the inspection in a
textbox[InspectionDate] then they use a combobox ([InspectionFreq]
3m,6m,y1,ect..) to select one of those options.
Now I have a query that calculates the [InspectionDate]+[InspectionFreq]
into an expression [NextInspdate].
This shows up on the form to let them know when the next inspection is.
I need the value of [NextInspDate] to be stored in the table
([MainUnitData]
its the record source of this form).

Lynn Trapp said:
hmmmmmmmm...that would be legitimate. Can you tell me a bit more about
what
you are trying to do?

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html
 
J

Joel

Well both [InspectionDate] and [InspectionFreq] will be changed quite often.
I am saving the history of this elsewere but it would take me a while to
convey it all into words.

And if you need my table structure that will take me quite a while to type
out also =)

Lynn Trapp said:
That doesn't look like a case where you are keeping the historical value of
a field that might otherwise change. As long as [InspectionDate] and
[InspectionFreq] remain constant for a given record, then you can always
calculate the next inspection date when you need it. Unless I'm missing
something, I see no reason for the MainUnitData needing the value of the
next inspection date. Perhaps if you would post your table structures, i
could see this better.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html



Joel said:
Thank You for your help.

Ok here it is:

I have a form that users enter the date of the inspection in a
textbox[InspectionDate] then they use a combobox ([InspectionFreq]
3m,6m,y1,ect..) to select one of those options.
Now I have a query that calculates the [InspectionDate]+[InspectionFreq]
into an expression [NextInspdate].
This shows up on the form to let them know when the next inspection is.
I need the value of [NextInspDate] to be stored in the table
([MainUnitData]
its the record source of this form).

Lynn Trapp said:
hmmmmmmmm...that would be legitimate. Can you tell me a bit more about
what
you are trying to do?

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html



I need to save it for a history of inspections.

:

If you can calculate it for your form, then you can calculate it
anywhere
else you need it. No need to store it.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html



I have a query that calculates 2 dates together and i have it showing
up
on
a
form.
How do I save the calculated value into a table?
 
L

Lynn Trapp

Well both [InspectionDate] and [InspectionFreq] will be changed quite
often.
I am saving the history of this elsewere but it would take me a while to
convey it all into words.


I understand that but, it seems to me, that NEXT inspection date is a one
time thing. It ceases to be the NEXT inspection date when the inspection is
done. Anyway, you don't need to give me the total table structure, just the
appropriate fields and, particularly, the target field where you want to
store this.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html



Joel said:
Well both [InspectionDate] and [InspectionFreq] will be changed quite
often.
I am saving the history of this elsewere but it would take me a while to
convey it all into words.

And if you need my table structure that will take me quite a while to type
out also =)

Lynn Trapp said:
That doesn't look like a case where you are keeping the historical value
of
a field that might otherwise change. As long as [InspectionDate] and
[InspectionFreq] remain constant for a given record, then you can always
calculate the next inspection date when you need it. Unless I'm missing
something, I see no reason for the MainUnitData needing the value of the
next inspection date. Perhaps if you would post your table structures, i
could see this better.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html



Joel said:
Thank You for your help.

Ok here it is:

I have a form that users enter the date of the inspection in a
textbox[InspectionDate] then they use a combobox ([InspectionFreq]
3m,6m,y1,ect..) to select one of those options.
Now I have a query that calculates the
[InspectionDate]+[InspectionFreq]
into an expression [NextInspdate].
This shows up on the form to let them know when the next inspection is.
I need the value of [NextInspDate] to be stored in the table
([MainUnitData]
its the record source of this form).

:

hmmmmmmmm...that would be legitimate. Can you tell me a bit more about
what
you are trying to do?

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html



I need to save it for a history of inspections.

:

If you can calculate it for your form, then you can calculate it
anywhere
else you need it. No need to store it.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html



I have a query that calculates 2 dates together and i have it
showing
up
on
a
form.
How do I save the calculated value into a table?
 
J

Joel

I think I am going at this all wrong.
Forget about saving the [NextInspDate].
How do I just get the [NextInspDate] to show up on a report?


Lynn Trapp said:
Well both [InspectionDate] and [InspectionFreq] will be changed quite
often.
I am saving the history of this elsewere but it would take me a while to
convey it all into words.


I understand that but, it seems to me, that NEXT inspection date is a one
time thing. It ceases to be the NEXT inspection date when the inspection is
done. Anyway, you don't need to give me the total table structure, just the
appropriate fields and, particularly, the target field where you want to
store this.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html



Joel said:
Well both [InspectionDate] and [InspectionFreq] will be changed quite
often.
I am saving the history of this elsewere but it would take me a while to
convey it all into words.

And if you need my table structure that will take me quite a while to type
out also =)

Lynn Trapp said:
That doesn't look like a case where you are keeping the historical value
of
a field that might otherwise change. As long as [InspectionDate] and
[InspectionFreq] remain constant for a given record, then you can always
calculate the next inspection date when you need it. Unless I'm missing
something, I see no reason for the MainUnitData needing the value of the
next inspection date. Perhaps if you would post your table structures, i
could see this better.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html



Thank You for your help.

Ok here it is:

I have a form that users enter the date of the inspection in a
textbox[InspectionDate] then they use a combobox ([InspectionFreq]
3m,6m,y1,ect..) to select one of those options.
Now I have a query that calculates the
[InspectionDate]+[InspectionFreq]
into an expression [NextInspdate].
This shows up on the form to let them know when the next inspection is.
I need the value of [NextInspDate] to be stored in the table
([MainUnitData]
its the record source of this form).

:

hmmmmmmmm...that would be legitimate. Can you tell me a bit more about
what
you are trying to do?

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html



I need to save it for a history of inspections.

:

If you can calculate it for your form, then you can calculate it
anywhere
else you need it. No need to store it.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html



I have a query that calculates 2 dates together and i have it
showing
up
on
a
form.
How do I save the calculated value into a table?
 
L

Lynn Trapp

Use the same calculation in the Query behind your report that you use for
your your form.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html



Joel said:
I think I am going at this all wrong.
Forget about saving the [NextInspDate].
How do I just get the [NextInspDate] to show up on a report?


Lynn Trapp said:
Well both [InspectionDate] and [InspectionFreq] will be changed quite
often.
I am saving the history of this elsewere but it would take me a while
to
convey it all into words.


I understand that but, it seems to me, that NEXT inspection date is a one
time thing. It ceases to be the NEXT inspection date when the inspection
is
done. Anyway, you don't need to give me the total table structure, just
the
appropriate fields and, particularly, the target field where you want to
store this.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html



Joel said:
Well both [InspectionDate] and [InspectionFreq] will be changed quite
often.
I am saving the history of this elsewere but it would take me a while
to
convey it all into words.

And if you need my table structure that will take me quite a while to
type
out also =)

:

That doesn't look like a case where you are keeping the historical
value
of
a field that might otherwise change. As long as [InspectionDate] and
[InspectionFreq] remain constant for a given record, then you can
always
calculate the next inspection date when you need it. Unless I'm
missing
something, I see no reason for the MainUnitData needing the value of
the
next inspection date. Perhaps if you would post your table structures,
i
could see this better.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html



Thank You for your help.

Ok here it is:

I have a form that users enter the date of the inspection in a
textbox[InspectionDate] then they use a combobox ([InspectionFreq]
3m,6m,y1,ect..) to select one of those options.
Now I have a query that calculates the
[InspectionDate]+[InspectionFreq]
into an expression [NextInspdate].
This shows up on the form to let them know when the next inspection
is.
I need the value of [NextInspDate] to be stored in the table
([MainUnitData]
its the record source of this form).

:

hmmmmmmmm...that would be legitimate. Can you tell me a bit more
about
what
you are trying to do?

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html



I need to save it for a history of inspections.

:

If you can calculate it for your form, then you can calculate it
anywhere
else you need it. No need to store it.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html



I have a query that calculates 2 dates together and i have it
showing
up
on
a
form.
How do I save the calculated value into a table?
 
Top