Access export to excel bug

[Access user]

My apologies for crossposting this, but I did not get any response in
microsoft.public.access

http://groups.google.com/group/micro...1bf56313b894d4

The specific problem is mentioned in the above post, but here is a
basic description of the problem.

When using saved queries that are used as part of a union query, the
UNION query does not export to excel successfully and prompts the user
to "enter parameter value" when no parameters are used. However, the
query works correctly when you simply run it in access, and it is
possible to export to other formats, but it consistently fails when
exporting to excel.

I know the description in my previous post is rather long, but I
wanted to provide as much information as I could.

If anyone has any ideas, can reproduce the error, or can point me to
someplace where I can submit this to Microsoft, I would appreciate it.

Thank you.

[Roger]

On May 29, 6:26*pm, Access user <[e-mail]:

My apologies for crossposting this, but I did not get any response in
microsoft.public.access

http://groups.google.com/group/micro...browse_thread/...

The specific problem is mentioned in the above post, but here is a
basic description of the problem.

When using saved queries that are used as part of a union query, the
UNION query does not export to excel successfully and prompts the user
to "enter parameter value" when no parameters are used. However, the
query works correctly when you simply run it in access, and it is
possible to export to other formats, but it consistently fails when
exporting to excel.

I know the description in my previous post is rather long, but I
wanted to provide as much information as I could.

If anyone has any ideas, can reproduce the error, or can point me to
someplace where I can submit this to Microsoft, I would appreciate it.

Thank you.

so isn't the solution to use shorter names ?

[Access user]

On May 30, 6:13*am, Roger <[e-mail]:

On May 29, 6:26*pm, Access user <[e-mail]:

My apologies for crossposting this, but I did not get any response in
microsoft.public.access

http://groups.google.com/group/micro...browse_thread/...

The specific problem is mentioned in the above post, but here is a
basic description of the problem.

When using saved queries that are used as part of a union query, the
UNION query does not export to excel successfully and prompts the user
to "enter parameter value" when no parameters are used. However, the
query works correctly when you simply run it in access, and it is
possible to export to other formats, but it consistently fails when
exporting to excel.

I know the description in my previous post is rather long, but I
wanted to provide as much information as I could.

If anyone has any ideas, can reproduce the error, or can point me to
someplace where I can submit this to Microsoft, I would appreciate it.

Thank you.

so isn't the solution to use shorter names ?

The point is, this works correctly when running the query, but fails
ONLY on the export. Since all of the query, table, and field names
fall within the length limit imposed by Access, this should not
happen. That is why I believe this is a bug.