Q: Use a temp table for a single field or ?

[John]

I have a form that prints a report for a weekly staff meeting. On the
form is an unbound field to enter the staff meeting date, which is
subsequently used as a parameter in the report's query data source.

I'd like to have this date stored/recalled so that when the user opens
the form to print the report for the staff meeting each week, the form
"recalls" the previously entered date. That way the user doesn't have
to look at the calendar or guess.

Will I need to create a table just to store this date, or is there a
better way?

[Steve Jorgensen]

Re: Q: Use a temp table for a single field or ?

You could make a table for this -type- of thing, and use different columns
or different rows to handle the different cases. Actually, though, I think
I would go for the table. If you have one setting you want to save today,
you may have more later, and it will be convenient if you have a table with
columns with the same names/types as you want to store.

Another option is to use the XML library to create and manage a settings
document in the same directory as the MDB. The advantage of this is that,
if you deploy a new copy of the database front-end, you don't erase the
user's preferences - they're still in the xml file.

On 21 Oct 2003 23:47:58 -0700, soundneedle@hot mail.com (John) wrote:
[color=blue]
>I have a form that prints a report for a weekly staff meeting. On the
>form is an unbound field to enter the staff meeting date, which is
>subsequently used as a parameter in the report's query data source.
>
>I'd like to have this date stored/recalled so that when the user opens
>the form to print the report for the staff meeting each week, the form
>"recalls" the previously entered date. That way the user doesn't have
>to look at the calendar or guess.
>
>Will I need to create a table just to store this date, or is there a
>better way?[/color]

[Terry Kreft]

Re: Use a temp table for a single field or ?

There are a number of ways you can store this information, but the easiest
is in a table.

Personally I create a generic "Control" table for these bits of unrelated
data that are needed for the application to run.

Terry

"John" <soundneedle@ho tmail.com> wrote in message
news:90fab935.0 310212247.446cf 022@posting.goo gle.com...[color=blue]
> I have a form that prints a report for a weekly staff meeting. On the
> form is an unbound field to enter the staff meeting date, which is
> subsequently used as a parameter in the report's query data source.
>
> I'd like to have this date stored/recalled so that when the user opens
> the form to print the report for the staff meeting each week, the form
> "recalls" the previously entered date. That way the user doesn't have
> to look at the calendar or guess.
>
> Will I need to create a table just to store this date, or is there a
> better way?[/color]

[Albert D. Kallal]

Re: Use a temp table for a single field or ?

Just create a table, and bind the form to the table with the one record. It
will automaticially remember the value, and it takes no code!

So, use a bound form! Assuming you have a standard split database, this
table can go in the front end, and thus you get a nice form that remembers
EACH USERS setting without having to write special code.


--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
kallal@msn.com

http://www.attcanada.net/~kallal.msn