<rfdjr1@[EMAIL PROTECTED]
> wrote in message
news:cnsm241g84nt555ebur7rcrt8oijfkom0v@[EMAIL PROTECTED]
> Okay, I've determined this much. A number of years ago, I had this
> database
> originally in DbaseIII, an old DOS program. Apparently when I got Office
> 2000, I
> converted or im****ted the DbaseIII data into Access. Not sure which.
Sorry
> for
> the confusion, but I just figured that out last night. However, ever
since
> the
> first conversion or im****t, I've used Access exclusively to enter my
CD's
> as I
> bought them. I don't know if this info helps or clouds the issue, but
> that's
> what happened. Thanks agin for the posts and help.
Whatever you think you are doing, the database to which you posted a link
has only one object, a link to an external DBase table... which table, of
course, is not in the download. If you have been "using Access to enter
the
data", it would seem that you have been opening that linked DBase table in
datasheet view, and entering records into the DBase table. It appears,
once
I reset the references to include the Microsoft Access DAO 3.6 Library,
and
copy in some code, and run it that you have in the root directory of your
C:
drive a folder named DBASEIII and in it, the source table for the linked
table CD_DISKS, which is named DBASEIII.DBF.
There is no Access table, so either you uploaded the wrong database for us
to, or you only linked not im****ted the DBase table.
As I see no Queries in the database, you'd need to tell us in detail how
you
are sorting the table... do you open it in datasheet view and select
sorting
from the toolbar?
My guess is that the first step toward correcting the problem you asked
about is to actually im****t that DBASEIII.DBF into a real, genuine Access
table. Then you could upload again and someone might be able to assist.
(Provided you give us detail steps of what you are doing to view and sort
the table.)
Easiest way, likely, is to create a new, empty Access database. On the
menu
File | Get External Data, and _carefully_ follow the prompts to IM****T it
into an Access table. It's possible that you'll find you no longer have
the
same problem when you work with the Access table.
Larry Linson
Microsoft Office Access MVP
|
