can you recreate an old record with same id?

[Robert Blackwell]

http://www.wowcentral.com/random/form.gif

When we load our dbase the first record that shows in that screenshot is
suppose to be the first contact id in the dbase. We used to have a record
with id 1883 called _test (as you see in the screen I recreated it and it's
now got a new id).

The problem though is that since the record was deleted the first record
that shows on the screen is of one of our actual customers.

Our dbase was never created to allow people to delete orders, so we had this
test account that would always show up first on the list. If you created an
order with another account but needed to delete it, you'd minimize the order
form, load the _test contact click new order and then it would transfer it
over to the _test contact (then I would press F11 and find those orders in
the dbase and manually delete them). I hope this makes sense.

So, what I want to do is to change the record id of the _test account so
it's 1883 or older so it would appear first.

does this make sense? I hope so because I didn't create the dbase and the
guy who did is long gone.

(btw, customers can't be deleted either except by f11 and manually going
into the dbase as I must have done by mistake, unless someone else did, I
haven't questioned the other person who might have done it because he didn't
come in today). It's not REALLY that big of a deal, but it would be nice if
somehow I could change the _test records id back to something lower then
1900.

I know I can change design of the table and change the primary key, and of
course backup the dbase 2 times and then work on one of the backups to work
on this issue, but the dbase is very relational dealing with customer
address information, orders, ordered items/qties/ credit card nubmers etc.

Is what I'm thinking of doing insane?

 

[Joseph Meehan]

http://www.wowcentral.com/random/form.gif

When we load our dbase the first record that shows in that screenshot
is suppose to be the first contact id in the dbase. We used to have a
record with id 1883 called _test (as you see in the screen I
recreated it and it's now got a new id).

The problem though is that since the record was deleted the first
record that shows on the screen is of one of our actual customers.

Our dbase was never created to allow people to delete orders, so we
had this test account that would always show up first on the list. If
you created an order with another account but needed to delete it,
you'd minimize the order form, load the _test contact click new order
and then it would transfer it over to the _test contact (then I would
press F11 and find those orders in the dbase and manually delete
them). I hope this makes sense.

So, what I want to do is to change the record id of the _test account
so it's 1883 or older so it would appear first.

does this make sense? I hope so because I didn't create the dbase and
the guy who did is long gone.

(btw, customers can't be deleted either except by f11 and manually
going into the dbase as I must have done by mistake, unless someone
else did, I haven't questioned the other person who might have done
it because he didn't come in today). It's not REALLY that big of a
deal, but it would be nice if somehow I could change the _test
records id back to something lower then 1900.

I know I can change design of the table and change the primary key,
and of course backup the dbase 2 times and then work on one of the
backups to work on this issue, but the dbase is very relational
dealing with customer address information, orders, ordered
items/qties/ credit card nubmers etc.

Is what I'm thinking of doing insane?

If I understand what you want to do, you should be able to set the sort
property of the form to sort the record you want first.

 

[Tony Toews]

The problem though is that since the record was deleted the first record
that shows on the screen is of one of our actual customers.

You can use a INSERT VALUES query to insert records with values in the
autonumber field.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Robert Blackwell]

Even if it's the primary key?

 

[John Vinson]

Even if it's the primary key?

Sure, just so long as the value you're inserting doesn't already exist
in the table.

 

[Robert Blackwell]

Okay great. That will work just perfect then. um, how do I do this?

I mean, I know how to write the script but where do I go to type and run it?

 

[John Vinson]

Okay great. That will work just perfect then. um, how do I do this?

I mean, I know how to write the script but where do I go to type and run it?

Create it as a new Query in the query definition window (use the
Append Query as the query type) and just run it from there, if this is
a once-only operation.

 

[Robert Blackwell]

Okay thanks.

 

[Robert Blackwell]

Okay I made the append query, everything was gravy.

Thanks.