Dear Microsoft: re: Error 3090...

[Guest]

Dear Microsoft,

Perhaps this is a feature you can add to a future version of Access?

When attempting to import a query as a table, I encountered the following
error:
"Resultant table not allowed to have more than one AutoNumber field. (Error
3090)"

This error arises because the query I am attempting to import as a table is
based upon multiple layers of sub-queries, and in the reulting recordset I
wish to show several columns which are indeed autonumbers from their
respective source tables in various subqueries.
It would be really neat if instead of just tossing up this error 3090 and
killing my import-to-table operation, Access instead did something like:

msgbox("WARNING! The query you are importing has multiple Autonumber fields,
and since only one autonumber field is permitted in a Table, Your query
cannot be imported unless you can either change the query or source table
field data type to something other than autonumbers, or you can permit the
export function to override the autonumber fields and change them ALL
automatically to Long Integer Data Types. Do you want to proceed and change
all the autonumbers to Long Integers, or do you wish to cancel the import
process for query: '<QueryNameHere>'?" <Convert Autonumbers to Long Integers
and Proceed> <Cancel>) ...and then did what the user requested.

Of course, I'm only speaking of the case when this import was fired off from
the Main Access UI. If it were done programmatically, I would hope that there
were an option flag on the import method call that would allow the automatic
conversion of AutoNumbers to Longs (only in cases where there are multiple
autonumber fields in the query) for the option where queries are being
imported to Tables.

 

[Guest]

Of course, I can (and will) code equivilant functionality to this request for
myself, but it would be really nice if this were "in the box" as it were, and
i can't see any good reason it shouldn't be.

 

[BruceM]

Just so you know, this is a volunteer users newsgroup. Your message is
unlikely to come to the attention of anybody who can act upon the suggestion
(not that Microsoft actively solicits feedback in any case, at least not to
my awareness).

 

[Guest]

Bruce,

Well, some MS folk DO read these newsgroups (at least occasionally) - I say
this on some good authority and based some previous personal experience.
....and MS also does sometimes take suggestions/solicit opinions on new
versions & features.
Since this is my only _current_ inroad to MS, this is the forum I chose.
....will this fall on fertile ears/ground...?? who knows?

 

[Duane Hookom]

You also have the attention of Access MVPs who like to think they have a
little more "clout" than average Access users .

 

[John Vinson]

You also have the attention of Access MVPs who like to think they have a
little more "clout" than average Access users .

.... although having seen the previews of the next release, I wonder
about that... :-{(

John W. Vinson[MVP]

 

[Duane Hookom]

Agreed. Next year should be interesting.

 

[Guest]

Duane & John,

Thanks for the replies.

....any thoughts on my wish? any hope to see anything like it in that "next
release" you've been able to preview? ...or should I not be holding my
breath? ;-)