PC Review


Reply
Thread Tools Rate Thread

Changing an AutoIncrement Field to a Long Integer Field and Back

 
 
Don
Guest
Posts: n/a
 
      8th Dec 2005


I realize this is a bit unorthodox and reflects a questionable table design,
but I am coming in on the end of this saga.......

We need to massage a small set of data to get to coincide with an old
system. In short, the new system uses an AutoIncrement field to assign an
order number. However, for tracking purposes, we need to ender some orders
from our old system. These old orders already have an order number.

In the table design, can I change the AutoIncrement field into a Long
Integer field, get my old data and set the order numbers accordingly, then
convert the field back to AutoIncrement? Key thing is that the change to
AutoIncrement does not renumber the orders -- will it do that? Once the old
orders are in the system, AutoIncrementing will be fine.

Thanks!

Don



 
Reply With Quote
 
 
 
 
Allen Browne
Guest
Posts: n/a
 
      8th Dec 2005
You can turn an AutoNumber into a Long, but then you cannot go back to
AutoNum again.

If you just want to add some numbers that are not already in the table, you
can do that with an Append query, even while the field remains an AutoNum.

--
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.

"Don" <(E-Mail Removed)> wrote in message
news:u4wAx1A$(E-Mail Removed)...
>
> I realize this is a bit unorthodox and reflects a questionable table
> design, but I am coming in on the end of this saga.......
>
> We need to massage a small set of data to get to coincide with an old
> system. In short, the new system uses an AutoIncrement field to assign an
> order number. However, for tracking purposes, we need to ender some
> orders from our old system. These old orders already have an order
> number.
>
> In the table design, can I change the AutoIncrement field into a Long
> Integer field, get my old data and set the order numbers accordingly, then
> convert the field back to AutoIncrement? Key thing is that the change to
> AutoIncrement does not renumber the orders -- will it do that? Once the
> old orders are in the system, AutoIncrementing will be fine.
>
> Thanks!
>
> Don



 
Reply With Quote
 
=?Utf-8?B?bXNjZXJ0aWZpZWQ=?=
Guest
Posts: n/a
 
      8th Dec 2005
I had to do a similar thing once. I created an autonumber column and a second
column called 'old number'. If the 'old number' column is null, the
autonumber column is the order number otherwise its the 'old number' column.

Obviously this causes problems with queries on the number but it's the only
solution I found for keeping the old numbers.

-Dorian


"Don" wrote:

>
>
> I realize this is a bit unorthodox and reflects a questionable table design,
> but I am coming in on the end of this saga.......
>
> We need to massage a small set of data to get to coincide with an old
> system. In short, the new system uses an AutoIncrement field to assign an
> order number. However, for tracking purposes, we need to ender some orders
> from our old system. These old orders already have an order number.
>
> In the table design, can I change the AutoIncrement field into a Long
> Integer field, get my old data and set the order numbers accordingly, then
> convert the field back to AutoIncrement? Key thing is that the change to
> AutoIncrement does not renumber the orders -- will it do that? Once the old
> orders are in the system, AutoIncrementing will be fine.
>
> Thanks!
>
> Don
>
>
>
>

 
Reply With Quote
 
Don
Guest
Posts: n/a
 
      9th Dec 2005
Thanks everyone!

I think I will use Allen's append query concept as a base to address the
issue.

Don






"Don" <(E-Mail Removed)> wrote in message
news:u4wAx1A$(E-Mail Removed)...
>
>
> I realize this is a bit unorthodox and reflects a questionable table

design,
> but I am coming in on the end of this saga.......
>
> We need to massage a small set of data to get to coincide with an old
> system. In short, the new system uses an AutoIncrement field to assign an
> order number. However, for tracking purposes, we need to ender some

orders
> from our old system. These old orders already have an order number.
>
> In the table design, can I change the AutoIncrement field into a Long
> Integer field, get my old data and set the order numbers accordingly, then
> convert the field back to AutoIncrement? Key thing is that the change to
> AutoIncrement does not renumber the orders -- will it do that? Once the

old
> orders are in the system, AutoIncrementing will be fine.
>
> Thanks!
>
> Don
>
>
>



 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Long Integer field size Selby Microsoft Access Getting Started 11 3rd Jun 2009 07:01 PM
FindFirst when field is Long Integer =?Utf-8?B?RWQgQmxvb20=?= Microsoft Access VBA Modules 4 29th Nov 2007 12:54 PM
Changing an AutoIncrement Field to a Long Integer Field and Back Don Microsoft Access External Data 3 9th Dec 2005 03:23 AM
Date field appear as long integer John D via AccessMonster.com Microsoft Access External Data 2 28th Nov 2005 06:02 PM
Can't create Integer field, a Long Integer is created instead? cbu Microsoft Access Database Table Design 1 2nd Jan 2004 04:58 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 08:07 PM.