You can also use variables. At some point before you need them you can
read them from field data. You can write them back when you're done.
Alternatively, you can just "hard-wire" them in the script if they are
never going to change.
Using variables saves you having to create yet another relationship
and maybe eliminate a few fields.
j.
On Sep 24, 2008, at 8:44 AM, Bruce Herbach wrote:
Hi Ron,
One method would be to set up a parameter table that is related to
your data through the X relationship. You can then setup a layout to
select values either by entering the data or drop down menus using
lists. Put a a button on the layout to run the report and have the
first steps pull the parameters for the report.
If you use a Global field to store the values and the database is
served, your changes to the field will only be in effect for the
session. Once you close the database and reopen the values will be
revert to the original setting. If you open the file locally, the
changes will be saved. This can be very helpful if you want a
standard starting point.
With a global field, the data in the parameter fields will be
available wen you are in find mode. If these are not global fields
you have to copy them to variables before entering find mode.
I hope this helps.
Bruce Herbach
Ron wrote:
I have a summary report that I would limited to a range of values.
The way I would do this in Access is to show a parameter screen
with controls to enter from – to values, which would be stored and
used in the Find to define the content of the layout.
I am not getting where to store these values for subsequent use: I
have tried inserting them in the layout table, and also in a
“variables” table, but that can’t be related.
Any info for me?
Thank you.
Ron Carr
--
Jonathan Fletcher
[EMAIL PROTECTED]
Project Foreman
NewMedia Construction Co.
