Not sorting after fixing conflicts...

  • Thread starter Thread starter Goobz
  • Start date Start date
G

Goobz

Hey all.. The other day I have to fix a crapload of Replica Conflicts
in my database. Now, when I click the "Next Record" button in my form,
instead of it going in numerical order by the first field like it did,
it jumps all over the place and has no order to it, except for record
order.

How can I get this back to being in numerical order of the first
record field when I click the next record button!?
 
Hey all.. The other day I have to fix a crapload of Replica Conflicts
in my database. Now, when I click the "Next Record" button in my form,
instead of it going in numerical order by the first field like it did,
it jumps all over the place and has no order to it, except for record
order.

How can I get this back to being in numerical order of the first
record field when I click the next record button!?
Click to expand...

A table HAS NO ORDER. A form based on a table will have its records presented
in whatever order Access finds convenient - it might be in disk storage order,
in Primary Key order (random, if your PK is an Autonumber in a replicated
database), or some other order.

If you want to see records in order you must base the form on a Query sorting
the records by some field or fields in your table that provide the desired
sequence.

John W. Vinson [MVP]
 
A table HAS NO ORDER. A form based on a table will have its records presented
in whatever order Access finds convenient - it might be in disk storage order,
in Primary Key order (random, if your PK is an Autonumber in a replicated
database), or some other order.

If you want to see records in order you must base the form on a Query sorting
the records by some field or fields in your table that provide the desired
sequence.

John W. Vinson [MVP]
Click to expand...

So it just happend to be coinsdence before!? It was probably because
they were inputted 1,2,3,4,5,6,etc. After the conflice, they were
input as whatever I take it!?
 
So it just happend to be coinsdence before!? It was probably because
they were inputted 1,2,3,4,5,6,etc. After the conflice, they were
input as whatever I take it!?
Click to expand...

One possible cause would be that the database was not replicated (and had
sequential autonumbers) before; after being replicated all the autonumbers
will have become random.

John W. Vinson [MVP]
 
One possible cause would be that the database was not replicated (and had
sequential autonumbers) before; after being replicated all the autonumbers
will have become random.

John W. Vinson [MVP]
Click to expand...

Makes perfect sense... Thanx for the input...
 
If you want to see records in order you must base the form on a
Query sorting the records by some field or fields in your table
that provide the desired sequence.
Click to expand...

Or assign a SortOrder to the form and turn it on.
 
One possible cause would be that the database was not replicated
(and had sequential autonumbers) before; after being replicated
all the autonumbers will have become random.
Click to expand...

Well, all *new* values, yes, but existing values are not changed by
converting the Autonumber to random.
 
Back
Top