By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,694 Members | 2,015 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,694 IT Pros & Developers. It's quick & easy.

Access 2007: exporting queries doesn't work

P: n/a
Hi all,

I use Access 2007 and have the following problems: when exporting
banal select queries (either to Excel or to a csv file) I find that
exporting often doesn't work and creates a file with the WHOLE
dataset, i.e. including those rows which the criteria of the query
excluded.

For example: let's say I have a database with sales by region. I
create a select query to only show sales from Europe. The query runs
fine, but when I export it, I get a file with data from all regions!

In these cases I find that if I close and restart Access, and then
export again, it usually - but not always - works.

Any idea why this is happening? Am i the only one experiencing this?
is it a known Access 2007 bug?

Thanks!

PS I do wish my company had not upgraded to Office 2007, at least not
before the release of the first service pack!
Dec 5 '07 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Can you provide more information about this:

a) Does the problem occur if you type a specific region into the Criteria
row under the Region field, and save the query before exporting?

b) Or does it only happen if you don't save the query?

c) Or are you talking about viewing the query results (datasheet), and
applying a filter?

Also, how do you perform the export:
a) Through the ribbon?

b) Using TransferSpreadsheet in code or a macro?

c) Other?

--
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:55**********************************@s8g2000p rg.googlegroups.com...
>
I use Access 2007 and have the following problems: when exporting
banal select queries (either to Excel or to a csv file) I find that
exporting often doesn't work and creates a file with the WHOLE
dataset, i.e. including those rows which the criteria of the query
excluded.

For example: let's say I have a database with sales by region. I
create a select query to only show sales from Europe. The query runs
fine, but when I export it, I get a file with data from all regions!

In these cases I find that if I close and restart Access, and then
export again, it usually - but not always - works.

Any idea why this is happening? Am i the only one experiencing this?
is it a known Access 2007 bug?

Thanks!

PS I do wish my company had not upgraded to Office 2007, at least not
before the release of the first service pack!
Dec 5 '07 #2

P: n/a
On 5 Dec, 14:10, "Allen Browne" <AllenBro...@SeeSig.Invalidwrote:
Can you provide more information about this:

a) Does the problem occur if you type a specific region into the Criteria
row under the Region field, and save the query before exporting?
Yes, but
b) Or does it only happen if you don't save the query?
It happened both saving and without saving the query before exporting
c) Or are you talking about viewing the query results (datasheet), and
applying a filter?
No
Also, how do you perform the export:
a) Through the ribbon?
Yes
b) Using TransferSpreadsheet in code or a macro?
No
c) Other?
No, just the ribbon. I must add that it happened with more than one
Access database, so I'm starting to think it is some sort of -
extremely serious - bug in Access. Microsoft should be sued for this
type of mistakes!
>
Dec 5 '07 #3

P: n/a
>Microsoft should be sued for this
type of mistakes!
I couldn't agree more but it will never happen. Software seems to
exempt from the protections that the consumer enjoys when purchasing
almost anything else. As long as consumers accept this situation, and
going on past performance that will be forever, nothing will ever
change.

Windows Vista (which they seem to have patched to a usable state now)
and Office 2007 are 2 classic examples of half baked software releases
from the world's largest software developer.

Dec 5 '07 #4

P: n/a
Thanks for clarifying.

This kind of problem should not occur if the query is *saved*, and I've
certainly never seen that occur.

Make sure that you have unchecked the boxes for Name AutoCorrect under:
Office Button | Access Options | Current Database
If these boxes are checked (as they are by default in a new database),
Access can get confused about the field names, and I have seen it apply
criteria incorrectly.

You want this off for other reasons as well:
http://allenbrowne.com/bug-03.html

After doing that, compact the database.

If the issue still occurs after that, post the SQL statement for the query.

--
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:01**********************************@e10g2000 prf.googlegroups.com...
On 5 Dec, 14:10, "Allen Browne" <AllenBro...@SeeSig.Invalidwrote:
>Can you provide more information about this:

a) Does the problem occur if you type a specific region into the Criteria
row under the Region field, and save the query before exporting?

Yes, but
>b) Or does it only happen if you don't save the query?

It happened both saving and without saving the query before exporting
>c) Or are you talking about viewing the query results (datasheet), and
applying a filter?

No
>Also, how do you perform the export:
a) Through the ribbon?

Yes
>b) Using TransferSpreadsheet in code or a macro?

No
>c) Other?

No, just the ribbon. I must add that it happened with more than one
Access database, so I'm starting to think it is some sort of -
extremely serious - bug in Access. Microsoft should be sued for this
type of mistakes!
Dec 6 '07 #5

This discussion thread is closed

Replies have been disabled for this discussion.