424,294 Members | 1,891 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,294 IT Pros & Developers. It's quick & easy.

"Enter parameter value" error when exporting to Excel (but not if to other formats)

P: n/a
Hi all,

I use Access 2007 and have come across this error a number of times.
I have two tables (customer information) which should contain -
ideally - the same data.
I create a query to compare them based on customer code. The fields
are something like:
Customer code
Balance - Table 1
Balance - Table 2
Difference (the difference of the 2 fields above)
and so on.

The query runs fine, so I guess there is no error in the expressions.
However, if I try to export to Excel, I get the message "Enter
parameter value", as though Access did not understand one of the
values in the expressions; however, the query did run fine. Also, if I
export to csv, I don't get this message.

Any idea? I am an Access novice, but this really makes no sense to me :
(

Oct 31 '07 #1
Share this Question
Share on Google+
3 Replies


P: n/a
When Access pops up the dialog asking you for the parameter, what is the
name it asks you for?

It may help if you post the SQL statement for the query too.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

<my********@googlemail.comwrote in message
news:11*********************@22g2000hsm.googlegrou ps.com...
Hi all,

I use Access 2007 and have come across this error a number of times.
I have two tables (customer information) which should contain -
ideally - the same data.
I create a query to compare them based on customer code. The fields
are something like:
Customer code
Balance - Table 1
Balance - Table 2
Difference (the difference of the 2 fields above)
and so on.

The query runs fine, so I guess there is no error in the expressions.
However, if I try to export to Excel, I get the message "Enter
parameter value", as though Access did not understand one of the
values in the expressions; however, the query did run fine. Also, if I
export to csv, I don't get this message.

Any idea? I am an Access novice, but this really makes no sense to me
Oct 31 '07 #2

P: n/a
On 31 Oct, 11:56, "Allen Browne" <AllenBro...@SeeSig.Invalidwrote:
When Access pops up the dialog asking you for the parameter, what is the
name it asks you for?
Access truncates the names in the window, so I cannot be sure. I tried
to enlarge the window, but I can't.
It may help if you post the SQL statement for the query too.
The SQL code is very long. I'll try creating a query with fewer fields
and, if the problem persists, post the SQL code for that. Thanks!

Btw, I still don't understand why I only get this message when
exporting and not when running the query.

Oct 31 '07 #3

P: n/a
If you saved the query as Query1, you may be able to get Access to tell you
about the parameters by opening the Immediate Window (Ctrl+G) and entering
lines like this:

? Currentdb.QueryDefs("MyQuery").Parameters.Count

? Currentdb.QueryDefs("MyQuery").Parameters(0).Name

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

<my********@googlemail.comwrote in message
news:11**********************@k79g2000hse.googlegr oups.com...
On 31 Oct, 11:56, "Allen Browne" <AllenBro...@SeeSig.Invalidwrote:
>When Access pops up the dialog asking you for the parameter, what is the
name it asks you for?

Access truncates the names in the window, so I cannot be sure. I tried
to enlarge the window, but I can't.
>It may help if you post the SQL statement for the query too.

The SQL code is very long. I'll try creating a query with fewer fields
and, if the problem persists, post the SQL code for that. Thanks!

Btw, I still don't understand why I only get this message when
exporting and not when running the query.
Oct 31 '07 #4

This discussion thread is closed

Replies have been disabled for this discussion.