Field 1 is multiple copies of single numbers, ascending, related to table A;
field two is unique date/time, descending, related to table B. This table C
of about 1600 records sorts properly EXCEPT for 15 records (intermingled)
where field two shows ascending. I have tried: installing sr2b, deleting and
reentering the tables B & C records, and swearing a lot. Any suggestions????

It's not clear to me what you're asking about. Is it that the order of the
records in your table isn't what you expect? Never assume anything about the
order of records in tables: tables are unorganized "sacks of data", where
the data's put wherever it fits. If the sequence of records is important,
you must ensure there are appropriate fields to sort on, and use a query
with an ORDER BY clause.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"Frustrated Phil" <Frustrated (E-Mail Removed)> wrote in
message news:03E46B05-D853-4EE1-99E8-(E-Mail Removed)...
> Field 1 is multiple copies of single numbers, ascending, related to table
> A;
> field two is unique date/time, descending, related to table B. This table
> C
> of about 1600 records sorts properly EXCEPT for 15 records (intermingled)
> where field two shows ascending. I have tried: installing sr2b, deleting
> and
> reentering the tables B & C records, and swearing a lot. Any
> suggestions????

On Sat, 26 May 2007 11:51:09 -0700, Frustrated Phil <Frustrated
(E-Mail Removed)> wrote:

>Field 1 is multiple copies of single numbers, ascending, related to table A;
>field two is unique date/time, descending, related to table B. This table C
>of about 1600 records sorts properly EXCEPT for 15 records (intermingled)
>where field two shows ascending. I have tried: installing sr2b, deleting and
>reentering the tables B & C records, and swearing a lot. Any suggestions????

Well, I'd suggest that you abandon the idea that records in a table *have* any
defined order. They don't. A table is an unordered "heap" of records; it will
be presented in whatever order the JET database engine finds convenient. Often
this will be in primary key order, but there's no guarantee.

If you want to see records in a particular order, you must - no option! - use
a Query sorting the fields in that order. Such a query will be updateable and
should not interfere with your use of the database.

John W. Vinson [MVP]

Frustrated Phil <Frustrated (E-Mail Removed)> wrote:

>Field 1 is multiple copies of single numbers, ascending, related to table A;
>field two is unique date/time, descending, related to table B. This table C
>of about 1600 records sorts properly EXCEPT for 15 records (intermingled)
>where field two shows ascending. I have tried: installing sr2b, deleting and
>reentering the tables B & C records, and swearing a lot. Any suggestions????

There was a bug at one point in time with a version of Jet which didn't handle
indexes with descending properly.

I'd double check that you have Jet 3.51 SP3 3.51.3328.0 installed. Although this may
have been a problem in Jet 4.0. Look in the \Windows\System or similar directory for
the above files. Then right click on the file >> Properties >> Version.

There is a similar problem here but I don't think this was it.
BUG: You may notice an incorrect sorted order when you sort the negative decimal
values in descending order in Access
http://support.microsoft.com/kb/837148/en-us

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Just note that the classic cause of this particular
problem is that the century digits are hidden
(short date format) and incorrect.

(david)


Frustrated Phil wrote:
> Field 1 is multiple copies of single numbers, ascending, related to table A;
> field two is unique date/time, descending, related to table B. This table C
> of about 1600 records sorts properly EXCEPT for 15 records (intermingled)
> where field two shows ascending. I have tried: installing sr2b, deleting and
> reentering the tables B & C records, and swearing a lot. Any suggestions????

DAVID <(E-Mail Removed)> wrote:

>Just note that the classic cause of this particular
>problem is that the century digits are hidden
>(short date format) and incorrect.

Good catch. I had forgotten about that as I always use yyyy-mm-dd on my system.

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Thank you. Someone else gave me a clue to explore.

"Douglas J. Steele" wrote:

> It's not clear to me what you're asking about. Is it that the order of the
> records in your table isn't what you expect? Never assume anything about the
> order of records in tables: tables are unorganized "sacks of data", where
> the data's put wherever it fits. If the sequence of records is important,
> you must ensure there are appropriate fields to sort on, and use a query
> with an ORDER BY clause.
>
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no private e-mails, please)
>
>
> "Frustrated Phil" <Frustrated (E-Mail Removed)> wrote in
> message news:03E46B05-D853-4EE1-99E8-(E-Mail Removed)...
> > Field 1 is multiple copies of single numbers, ascending, related to table
> > A;
> > field two is unique date/time, descending, related to table B. This table
> > C
> > of about 1600 records sorts properly EXCEPT for 15 records (intermingled)
> > where field two shows ascending. I have tried: installing sr2b, deleting
> > and
> > reentering the tables B & C records, and swearing a lot. Any
> > suggestions????
>
>
>

Thank you.

"John W. Vinson" wrote:

> On Sat, 26 May 2007 11:51:09 -0700, Frustrated Phil <Frustrated
> (E-Mail Removed)> wrote:
>
> >Field 1 is multiple copies of single numbers, ascending, related to table A;
> >field two is unique date/time, descending, related to table B. This table C
> >of about 1600 records sorts properly EXCEPT for 15 records (intermingled)
> >where field two shows ascending. I have tried: installing sr2b, deleting and
> >reentering the tables B & C records, and swearing a lot. Any suggestions????
>
> Well, I'd suggest that you abandon the idea that records in a table *have* any
> defined order. They don't. A table is an unordered "heap" of records; it will
> be presented in whatever order the JET database engine finds convenient. Often
> this will be in primary key order, but there's no guarantee.
>
> If you want to see records in a particular order, you must - no option! - use
> a Query sorting the fields in that order. Such a query will be updateable and
> should not interfere with your use of the database.
>
> John W. Vinson [MVP]
>

Thank you. I won't have a chance to check for a while, but suspect that's
it!!!

"DAVID" wrote:

> Just note that the classic cause of this particular
> problem is that the century digits are hidden
> (short date format) and incorrect.
>
> (david)
>
>
> Frustrated Phil wrote:
> > Field 1 is multiple copies of single numbers, ascending, related to table A;
> > field two is unique date/time, descending, related to table B. This table C
> > of about 1600 records sorts properly EXCEPT for 15 records (intermingled)
> > where field two shows ascending. I have tried: installing sr2b, deleting and
> > reentering the tables B & C records, and swearing a lot. Any suggestions????
>

Thank you. I'll double check, but suspect David spotted my error.

"Tony Toews [MVP]" wrote:

> Frustrated Phil <Frustrated (E-Mail Removed)> wrote:
>
> >Field 1 is multiple copies of single numbers, ascending, related to table A;
> >field two is unique date/time, descending, related to table B. This table C
> >of about 1600 records sorts properly EXCEPT for 15 records (intermingled)
> >where field two shows ascending. I have tried: installing sr2b, deleting and
> >reentering the tables B & C records, and swearing a lot. Any suggestions????
>
> There was a bug at one point in time with a version of Jet which didn't handle
> indexes with descending properly.
>
> I'd double check that you have Jet 3.51 SP3 3.51.3328.0 installed. Although this may
> have been a problem in Jet 4.0. Look in the \Windows\System or similar directory for
> the above files. Then right click on the file >> Properties >> Version.
>
> There is a similar problem here but I don't think this was it.
> BUG: You may notice an incorrect sorted order when you sort the negative decimal
> values in descending order in Access
> http://support.microsoft.com/kb/837148/en-us
>
> 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
> Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
>