Serious problem with reports introduced in Access 2007

[Michael Matuszak]

There is a problem that I have discovered with Access 2007 that I have only
found reported once – at UtterAccess – but it was somewhat dismissed there by
an Access MVP. I also reported this in the microsoft.public.access.reports
discussion group at the beginning of the month, and the only reply I received
was that I should use a form to collect the parameters. I know the unbound
form trick is an option from an article on the topic on Allen Browne's site,
but it is not practical to do this to resolve the issue for 200 or so clients
my company has provided such reports to.

The problem: If you try to open a report that has a SQL statement with a
PARAMETERS clause as the Record Source, Access 2007 throws Error 3194. If you
use a named query with the exact same SQL for the Record Source, no error.
This was not an issue in Access 2003 or earlier.

To see a simple example of this, download this file:
http://home.comcast.net/~mmatuszak/ParameterClauseThrowsError3194.zip

Any ideas on how I can bring this to Microsoft’s attention, since raising
the issue in discussion groups doesn’t seem to be working?


----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...-9934-8eda8dca6d77&dg=microsoft.public.access

 

[UpRider]

Mike, you could simply remove the parameter clause:

SELECT * FROM Table1 WHERE [TestDate]=[For what TestDate?];

In your example this worked fine.

UpRider

 

[Michael Matuszak]

My example was for demonstration purposes only. I do not have the option of
simply removing exixting PARAMETERS clauses from report recordsources for
over 200 clients.

Mike, you could simply remove the parameter clause:

SELECT * FROM Table1 WHERE [TestDate]=[For what TestDate?];

In your example this worked fine.

UpRider

There is a problem that I have discovered with Access 2007 that I have
only
found reported once - at UtterAccess - but it was somewhat dismissed there
by
an Access MVP. I also reported this in the microsoft.public.access.reports
discussion group at the beginning of the month, and the only reply I
received
was that I should use a form to collect the parameters. I know the unbound
form trick is an option from an article on the topic on Allen Browne's
site,
but it is not practical to do this to resolve the issue for 200 or so
clients
my company has provided such reports to.

The problem: If you try to open a report that has a SQL statement with a
PARAMETERS clause as the Record Source, Access 2007 throws Error 3194. If
you
use a named query with the exact same SQL for the Record Source, no error.
This was not an issue in Access 2003 or earlier.

To see a simple example of this, download this file:
http://home.comcast.net/~mmatuszak/ParameterClauseThrowsError3194.zip

Any ideas on how I can bring this to Microsoft's attention, since raising
the issue in discussion groups doesn't seem to be working?


----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow
this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...-9934-8eda8dca6d77&dg=microsoft.public.access