Ordering records in form view

[gglazer]

I have a database which consists of a number of tables. One is called
"People" and contains demographic/contact data and another is called
"Memberships" which contains information about their membership level, date
purchased, etc. The ID from the People table is a foreign key in Memberships.

The form for entering data into Memberships has boxes for the various
Memberships field and a drop down which allows me to select the ID from
People based given the name (e.g., it uses a select in the source data).

The problem is that when I go to the last record in the form by pressing the
">|" button, it is NOT the last record in the Memberships table, rather it is
somewhere 2/3rds along the way. Oddly, it increments when a new person is
added, e.g., if there were 52 rows, record 41 is at the end, when I add a
record making it 53, the new end is 42.

Is there a way of making the form go to the end as defined as the max record
number in Memberships?

Thanks,

Glenn

 

[Rick Brandt]

I have a database which consists of a number of tables. One is called
"People" and contains demographic/contact data and another is called
"Memberships" which contains information about their membership
level, date purchased, etc. The ID from the People table is a
foreign key in Memberships.

The form for entering data into Memberships has boxes for the various
Memberships field and a drop down which allows me to select the ID
from People based given the name (e.g., it uses a select in the
source data).

The problem is that when I go to the last record in the form by
pressing the ">|" button, it is NOT the last record in the
Memberships table, rather it is somewhere 2/3rds along the way.
Oddly, it increments when a new person is added, e.g., if there were
52 rows, record 41 is at the end, when I add a record making it 53,
the new end is 42.

Is there a way of making the form go to the end as defined as the max
record number in Memberships?

Thanks,

Glenn

Tables have no reliable inherant order. You have to explicitly tell Access
to impose an order. For a form the simplest and most robust way to do that
is to bind the form to a SELECT query rather than the table and in the
SELECT query set the order that you want.

 

[gglazer]

Tables have no reliable inherant order. You have to explicitly tell Access
to impose an order. For a form the simplest and most robust way to do that
is to bind the form to a SELECT query rather than the table and in the
SELECT query set the order that you want.

Hi, Rick.

I think I need the extra step (binding) a little more explicitly said. I
tried playing around with the box properties a bit, but I only got things
like "#NAME" in my entry boxes. I think I set it for updating the query
rather than the table. In any case, I was able to revert it back, but not
sure how to follow your instruction above.

Thanks,

Glenn