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

Resultant tables not allowed to have more than one autonumber field!

P: n/a
Hi:

I am combining two tables in a query, extracting some fields, and attempting to create a
new table. This process is way down the line form the original tables, and some of the
fields were auto number fields originally (yes I am using those for some system level
identification of records). I have no intention of giving the new table any auto number
fields of its own, but I am getting an objection from that system that "Resultant tables
not allowed to have more than one auto number field"

Can someone tell me how to get round this boulder in the path of progress?

Thanks

JOhn baker
Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
I t tested this, it should work for you also.

The datatype of the original source is being passed into the new table
being built. So, if you convert the datatype to Long (which is the
integer data type equiv. of the Auto Num field), it will cast the new
table's field as long, and avoid your problem.

In my test, using a table with an AutoNum field called AssignmentID, I
used this generated field in the query:
ID: CLng([AssignmentID])

In SQL, it's SELECT CLng([AssignmentID]) AS ID, (etc.) FROM ...

Good Luck,
Bruce Pick

John Baker wrote:
Hi:

I am combining two tables in a query, extracting some fields, and attempting to create a
new table. This process is way down the line form the original tables, and some of the
fields were auto number fields originally (yes I am using those for some system level
identification of records). I have no intention of giving the new table any auto number
fields of its own, but I am getting an objection from that system that "Resultant tables
not allowed to have more than one auto number field"

Can someone tell me how to get round this boulder in the path of progress?

Thanks

JOhn baker

Nov 12 '05 #2

P: n/a
Thanks
Bruce Pick <br********@comcast.net> wrote:
I t tested this, it should work for you also.

The datatype of the original source is being passed into the new table
being built. So, if you convert the datatype to Long (which is the
integer data type equiv. of the Auto Num field), it will cast the new
table's field as long, and avoid your problem.

In my test, using a table with an AutoNum field called AssignmentID, I
used this generated field in the query:
ID: CLng([AssignmentID])

In SQL, it's SELECT CLng([AssignmentID]) AS ID, (etc.) FROM ...

Good Luck,
Bruce Pick

John Baker wrote:
Hi:

I am combining two tables in a query, extracting some fields, and attempting to create a
new table. This process is way down the line form the original tables, and some of the
fields were auto number fields originally (yes I am using those for some system level
identification of records). I have no intention of giving the new table any auto number
fields of its own, but I am getting an objection from that system that "Resultant tables
not allowed to have more than one auto number field"

Can someone tell me how to get round this boulder in the path of progress?

Thanks

JOhn baker


Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.