Reserved error (-3007); there is no message for this error.

  • Thread starter Thread starter Mark Burns
  • Start date Start date
M

Mark Burns

I get the above error message when opening a report (preview)

The query uses a parameterized crosstab query (between {Enter Date1:] amd
[Enter Date2:]) outer joined to another parameterized query (same parameters
and useage).

The crosstab query's fields are used in the outermost group summary band of
the report bound to text boxes (the field names are consistent as they are
table-derived form a pull-down combobox)

Any help/advice (other than "Don't do that if it hurts")?

PS. the query runs absolutely perfectly on its own.
Access XP w/ SP-2

- Mark
 
PPS. Changing the query to eliminate the outer join (converting to an inner
join) had no effect on the error.

Mark Burns said:
PS. The error appears after Access prompts for the parameter values.

Mark Burns said:
I get the above error message when opening a report (preview)

The query uses a parameterized crosstab query (between {Enter Date1:] amd
[Enter Date2:]) outer joined to another parameterized query (same parameters
and useage).

The crosstab query's fields are used in the outermost group summary band of
the report bound to text boxes (the field names are consistent as they are
table-derived form a pull-down combobox)

Any help/advice (other than "Don't do that if it hurts")?

PS. the query runs absolutely perfectly on its own.
Access XP w/ SP-2

- Mark
 
Hi Mark,

Thanks for your post. According to your description, I understand when you
open a report using crosstab query with parameters, you encountered the
following query:
"Reserved error (-3007); there is no message for this error."

What is the version of Access on your side? Please apply the latest version
of Service pack firstly for your version of Jet engine. For Access 97, the
version of Jet engine is 3.5, for Access 2000 or later, the Jet engine is
4.0.

Does it fix your problem? If not, I would like to know what the SQL
statements of the crosstab query are. It is appreciated that you can
provide a sample query showing this problem in the northwind.mdb sample
database so that I can fully understand what your concern is.

Thank for posting in community.

Sincerely,

Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Replies inline:

"Yuan Shao" said:
Hi Mark,

Thanks for your post. According to your description, I understand when you
open a report using crosstab query with parameters, you encountered the
following query:
"Reserved error (-3007); there is no message for this error."

What is the version of Access on your side?

Access 2002 (ver. 10.4302.4219) SP-2
Please apply the latest version
of Service pack firstly for your version of Jet engine. For Access 97, the
version of Jet engine is 3.5, for Access 2000 or later, the Jet engine is
4.0.

Referencing: DAO360.DLL Ver.:03.60.2521.8 (3/15/1999 12:00AM)

Loaded: MSJet40.DLL Ver.:4.00.7328.0 (9/8/2003 9:56PM)
Does it fix your problem? If not, I would like to know what the SQL
statements of the crosstab query are. It is appreciated that you can
provide a sample query showing this problem in the northwind.mdb sample
database so that I can fully understand what your concern is.

I may not be able to duplicate in it Northwind because I'm not that familiar
with that sample DB.
If you want, I may be able to mock up a version of our db that illustrates
the problem though.
(It'll have to be treated confidentially, of course, so please eMail me
privately if you want me to do that.)
Thank for posting in community.

Thanks for being here to answer!
 
Hi Mark,

Thanks for your update. Due to the nature of this issue, it is hard for me
to fully understand and troubleshoot it in detail without the sample Access
database. Please create a sample database showing this problem and send it
to me at (e-mail address removed) so that I can perform further research.

For some security reason, my email server will block the mdb file,
therefore, please change the file extension from mdb to zip before you send
it to me. If it is larger than 3 MB, please use other tools, such as
WinZip, to compress it and then send it to me.

I am looking forward to hearing from you soon.
Thank you,

Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Hi Mark,

Thanks for your update and the sample database you kindly provided. After
reviewing the underlying query and report in the sample database, I make
the following changes in your Access database and the report seems fine
now.

1. Using the "Advertisng Leads By AE and Discipline Query XT - Sample"
query with parameter sunderlying the "Advertisng Leads By AE and Discipline
Query" is not necessary. The recordset retrieving from the query in two
situations (having parameters or not) are same. Therefore I removed the
parameters from the "Advertisng Leads By AE and Discipline Query XT -
Sample" query. If you do want to use the "Advertisng Leads By AE and
Discipline Query XT - Sample" query with parameter for other purposes,
please create a new query without parameter as the underlying query of the
"Advertisng Leads By AE and Discipline Query" query.

2. Please specify the table for the scheduled field used in the following
control:
1. "Interview Scheduled" Check Box.
2. "txtSched" Text Box.

Or, you will get the following error message "The specified field
'Scheduled' could refer to more than one table listed in the FROM clause of
your SQL statement".

Also, for your convenience, I have sent the changed sample database back to
you. Please let me know if it can fix your problem.

Regards,

Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Michael,

Thanks!

BTW, I really appreciate the way Microsoft is (or at least, you are) taking
the time and energy to participate here in the newsgroups. I, for one,
really appreciate your efforts here.
Thanks again!

PS. (any idea why this wound up generating an unknown error message rather
than a more useful error message?)
 
Hi Mark,

I am glad to hear that the sample database I provided makes sense for you
and thank you for your feedback. Due to the complex of this query and
report, it seems hard to narrow down to the accurate root cause of this
problem. Thanks for your understanding. However, based on my research, it
is suspected this error is caused by the Ambiguous column reference, such
as scheduled filed, and logic mess of the complex parameter query when it
was performed under the report.

Thank you,

Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Back
Top