Has anyone seen this behaviour? What might it be?

I have a report that is set up as follows...

A unbound form collects from and to date for the report.

The data source for the report is bound to a query that has the parameters
of from and to date from the unbound form.

On one machine Win98 Access 2002...
database is Access 2000 format

This has only been witnessed on this one machine, it has occurred two times
that I know of. The user runs a report, prints it, closes it. Then runs
the report again, changing the dates on the parameter form. The report that
comes out, shows the new dates as the criteria of the report (coming
directly from the unbound form), but the data that the report is based on is
the same data that was used on the previous report run. It's like the query
didn't refresh when the report was run the second time. Is there something
that I can do to fix this. The query should close when the report closes,
therefore I don't see how requery might work. So what should I do?

All help is appreciated, thank you.

Are you hiding the form that you input the date in so that the query can
still see the form but it looks closed? If so, are you closing the form in
the close event of the report?

Since the query wasn't open by itself, it was just used by the report and
should therefore be closed when the report closes, it makes me suspect that
the report isn't closing. If the report gets its dates directly from the
form, then that has nothing to do with the query. If the form is closed in
the report's Close event, then that code is running - at least to that
point.

My first guess would be that something is corrupted in the front-end file on
that computer. Try copying a known good copy of the file to that computer.
Also, make sure that the latest patches for Windows, Office, Jet, and MDAC
have been installed on that computer and that your video and printer drivers
are up to date on that computer.

For the Windows updates, go to http://windowsupdate.microsoft.com; for the
Office updates, go to http://office.microsoft.com and click on Check for
Updates. For the Jet and MDAC updates, check he
http://msdn.microsoft.com/data/downl...s/default.aspx

--
Wayne Morgan
MS Access MVP


"tw" wrote in message
...
I have a report that is set up as follows...

A unbound form collects from and to date for the report.

The data source for the report is bound to a query that has the parameters
of from and to date from the unbound form.

On one machine Win98 Access 2002...
database is Access 2000 format

This has only been witnessed on this one machine, it has occurred two
times that I know of. The user runs a report, prints it, closes it. Then
runs the report again, changing the dates on the parameter form. The
report that comes out, shows the new dates as the criteria of the report
(coming directly from the unbound form), but the data that the report is
based on is the same data that was used on the previous report run. It's
like the query didn't refresh when the report was run the second time. Is
there something that I can do to fix this. The query should close when
the report closes, therefore I don't see how requery might work. So what
should I do?

All help is appreciated, thank you.

I keep the form visible, and I do close it in the close event of the report.

I also suspected that the report might not be closing. So I tested it on my
machine leaving the report open and running it again. When I do that, it
doesn't matter that I've changed the dates in the parameter form. The
report is remains unchanged with the correct dates and original data from
the first run of the report. The second report isn't even attempted. This
isn't what is happening.

On her machine the data remains the same from the original run of the
report, but the dates on the report to show what criteria was used, changes
to the new dates entered on the form. That tells me the query is the
problem, it is not being regenerated even though the report sees the new
dates.

Report example below
First run...

Payroll Report (the report title)
Payroll Date Range: 06/15/05 - 06/30/05 (these dates come from the unbound
form)

Detail (this data comes from the query that uses the dates from the unbound
form)
Employee HoursBilled
Emp1 47
Emp2 49
Emp3 61
Emp4 80

Second run...
Payroll Report (the report title)
Payroll Date Range: 06/25/05 - 06/30-05 (these are the new dates entered
into the unbound form)

Detail (this data comes from the query that uses the dates from the unbound
form, but it is still using the orignal dates the query has not changed)
Employee HoursBilled
Emp1 47
Emp2 49
Emp3 61
Emp4 80

The detail remains the same (it should be different... data checked, report
and query work fine on my machine), and it does not consistantly mess up on
her machine.
this is what the detail should be

Detail (using the new dates entered on the form)
Employee HoursBilled
Emp1 15
Emp2 10
Emp3 20
Emp4 22.5

The parameters are used in the query to filter data not in the report. The
report only uses the dates from the form qualify the data on the report so
that the readers of the report know what criteria was used when the report
was run.

The patches and drivers are all up to date on that machine.


I suspected the report not closing as well, but I tested the report on my
machine, not closing it, and running it again
"Wayne Morgan" wrote in message
...
Are you hiding the form that you input the date in so that the query can
still see the form but it looks closed? If so, are you closing the form in
the close event of the report?

Since the query wasn't open by itself, it was just used by the report and
should therefore be closed when the report closes, it makes me suspect
that the report isn't closing. If the report gets its dates directly from
the form, then that has nothing to do with the query. If the form is
closed in the report's Close event, then that code is running - at least
to that point.

My first guess would be that something is corrupted in the front-end file
on that computer. Try copying a known good copy of the file to that
computer. Also, make sure that the latest patches for Windows, Office,
Jet, and MDAC have been installed on that computer and that your video and
printer drivers are up to date on that computer.

For the Windows updates, go to http://windowsupdate.microsoft.com; for the
Office updates, go to http://office.microsoft.com and click on Check for
Updates. For the Jet and MDAC updates, check he
http://msdn.microsoft.com/data/downl...s/default.aspx

--
Wayne Morgan
MS Access MVP


"tw" wrote in message
...
I have a report that is set up as follows...

A unbound form collects from and to date for the report.

The data source for the report is bound to a query that has the
parameters of from and to date from the unbound form.

On one machine Win98 Access 2002...
database is Access 2000 format

This has only been witnessed on this one machine, it has occurred two
times that I know of. The user runs a report, prints it, closes it.
Then runs the report again, changing the dates on the parameter form.
The report that comes out, shows the new dates as the criteria of the
report (coming directly from the unbound form), but the data that the
report is based on is the same data that was used on the previous report
run. It's like the query didn't refresh when the report was run the
second time. Is there something that I can do to fix this. The query
should close when the report closes, therefore I don't see how requery
might work. So what should I do?

All help is appreciated, thank you.

I don't do it that way, so I haven't seen this, but the probable
method to fix it is to reset the recordsource of the report in
the open event of the report:

me.recordsource = me.recordsource

Since the query is not unloading correctly, you may see a
memory leak if you do this repeatedly on her machine.


(david)

"tw" wrote in message
...
I keep the form visible, and I do close it in the close event of the
report.

I also suspected that the report might not be closing. So I tested it on
my machine leaving the report open and running it again. When I do that,
it doesn't matter that I've changed the dates in the parameter form. The
report is remains unchanged with the correct dates and original data from
the first run of the report. The second report isn't even attempted.
This isn't what is happening.

On her machine the data remains the same from the original run of the
report, but the dates on the report to show what criteria was used,
changes to the new dates entered on the form. That tells me the query is
the problem, it is not being regenerated even though the report sees the
new dates.

Report example below
First run...

Payroll Report (the report title)
Payroll Date Range: 06/15/05 - 06/30/05 (these dates come from the unbound
form)

Detail (this data comes from the query that uses the dates from the
unbound form)
Employee HoursBilled
Emp1 47
Emp2 49
Emp3 61
Emp4 80

Second run...
Payroll Report (the report title)
Payroll Date Range: 06/25/05 - 06/30-05 (these are the new dates entered
into the unbound form)

Detail (this data comes from the query that uses the dates from the
unbound form, but it is still using the orignal dates the query has not
changed)
Employee HoursBilled
Emp1 47
Emp2 49
Emp3 61
Emp4 80

The detail remains the same (it should be different... data checked,
report and query work fine on my machine), and it does not consistantly
mess up on her machine.
this is what the detail should be

Detail (using the new dates entered on the form)
Employee HoursBilled
Emp1 15
Emp2 10
Emp3 20
Emp4 22.5

The parameters are used in the query to filter data not in the report.
The report only uses the dates from the form qualify the data on the
report so that the readers of the report know what criteria was used when
the report was run.

The patches and drivers are all up to date on that machine.


I suspected the report not closing as well, but I tested the report on my
machine, not closing it, and running it again
"Wayne Morgan" wrote in
message ...
Are you hiding the form that you input the date in so that the query can
still see the form but it looks closed? If so, are you closing the form
in the close event of the report?

Since the query wasn't open by itself, it was just used by the report and
should therefore be closed when the report closes, it makes me suspect
that the report isn't closing. If the report gets its dates directly from
the form, then that has nothing to do with the query. If the form is
closed in the report's Close event, then that code is running - at least
to that point.

My first guess would be that something is corrupted in the front-end file
on that computer. Try copying a known good copy of the file to that
computer. Also, make sure that the latest patches for Windows, Office,
Jet, and MDAC have been installed on that computer and that your video
and printer drivers are up to date on that computer.

For the Windows updates, go to http://windowsupdate.microsoft.com; for
the Office updates, go to http://office.microsoft.com and click on Check
for Updates. For the Jet and MDAC updates, check he
http://msdn.microsoft.com/data/downl...s/default.aspx

--
Wayne Morgan
MS Access MVP


"tw" wrote in message
...
I have a report that is set up as follows...

A unbound form collects from and to date for the report.

The data source for the report is bound to a query that has the
parameters of from and to date from the unbound form.

On one machine Win98 Access 2002...
database is Access 2000 format

This has only been witnessed on this one machine, it has occurred two
times that I know of. The user runs a report, prints it, closes it.
Then runs the report again, changing the dates on the parameter form.
The report that comes out, shows the new dates as the criteria of the
report (coming directly from the unbound form), but the data that the
report is based on is the same data that was used on the previous report
run. It's like the query didn't refresh when the report was run the
second time. Is there something that I can do to fix this. The query
should close when the report closes, therefore I don't see how requery
might work. So what should I do?

All help is appreciated, thank you.

I'll try this. It may be a while before we see if this works. Its only
happened two times in about 3 months so it's hard to track the cause.

"david epsom dot com dot au" david@epsomdotcomdotau wrote in message
...
I don't do it that way, so I haven't seen this, but the probable
method to fix it is to reset the recordsource of the report in
the open event of the report:

me.recordsource = me.recordsource

Since the query is not unloading correctly, you may see a
memory leak if you do this repeatedly on her machine.


(david)

"tw" wrote in message
...
I keep the form visible, and I do close it in the close event of the
report.

I also suspected that the report might not be closing. So I tested it on
my machine leaving the report open and running it again. When I do that,
it doesn't matter that I've changed the dates in the parameter form. The
report is remains unchanged with the correct dates and original data from
the first run of the report. The second report isn't even attempted.
This isn't what is happening.

On her machine the data remains the same from the original run of the
report, but the dates on the report to show what criteria was used,
changes to the new dates entered on the form. That tells me the query is
the problem, it is not being regenerated even though the report sees the
new dates.

Report example below
First run...

Payroll Report (the report title)
Payroll Date Range: 06/15/05 - 06/30/05 (these dates come from the
unbound form)

Detail (this data comes from the query that uses the dates from the
unbound form)
Employee HoursBilled
Emp1 47
Emp2 49
Emp3 61
Emp4 80

Second run...
Payroll Report (the report title)
Payroll Date Range: 06/25/05 - 06/30-05 (these are the new dates entered
into the unbound form)

Detail (this data comes from the query that uses the dates from the
unbound form, but it is still using the orignal dates the query has not
changed)
Employee HoursBilled
Emp1 47
Emp2 49
Emp3 61
Emp4 80

The detail remains the same (it should be different... data checked,
report and query work fine on my machine), and it does not consistantly
mess up on her machine.
this is what the detail should be

Detail (using the new dates entered on the form)
Employee HoursBilled
Emp1 15
Emp2 10
Emp3 20
Emp4 22.5

The parameters are used in the query to filter data not in the report.
The report only uses the dates from the form qualify the data on the
report so that the readers of the report know what criteria was used when
the report was run.

The patches and drivers are all up to date on that machine.


I suspected the report not closing as well, but I tested the report on my
machine, not closing it, and running it again
"Wayne Morgan" wrote in
message ...
Are you hiding the form that you input the date in so that the query can
still see the form but it looks closed? If so, are you closing the form
in the close event of the report?

Since the query wasn't open by itself, it was just used by the report
and should therefore be closed when the report closes, it makes me
suspect that the report isn't closing. If the report gets its dates
directly from the form, then that has nothing to do with the query. If
the form is closed in the report's Close event, then that code is
running - at least to that point.

My first guess would be that something is corrupted in the front-end
file on that computer. Try copying a known good copy of the file to that
computer. Also, make sure that the latest patches for Windows, Office,
Jet, and MDAC have been installed on that computer and that your video
and printer drivers are up to date on that computer.

For the Windows updates, go to http://windowsupdate.microsoft.com; for
the Office updates, go to http://office.microsoft.com and click on Check
for Updates. For the Jet and MDAC updates, check he
http://msdn.microsoft.com/data/downl...s/default.aspx

--
Wayne Morgan
MS Access MVP


"tw" wrote in message
...
I have a report that is set up as follows...

A unbound form collects from and to date for the report.

The data source for the report is bound to a query that has the
parameters of from and to date from the unbound form.

On one machine Win98 Access 2002...
database is Access 2000 format

This has only been witnessed on this one machine, it has occurred two
times that I know of. The user runs a report, prints it, closes it.
Then runs the report again, changing the dates on the parameter form.
The report that comes out, shows the new dates as the criteria of the
report (coming directly from the unbound form), but the data that the
report is based on is the same data that was used on the previous
report run. It's like the query didn't refresh when the report was run
the second time. Is there something that I can do to fix this. The
query should close when the report closes, therefore I don't see how
requery might work. So what should I do?

All help is appreciated, thank you.