Recently, the record selector in my (Wizard-generated) Order Entry database has decided not to work as it originally had. When there were multiple orders displayed in the "Orders by Customer subform", the record selector used to point to the order that was just edited (or created). Now, however, it points to the first (top) record.

I don't have a clue as to where to begin looking for the property that tells this record selector how to behave. Any ideas?

To be clear, the database design was generated from Access's Wizard that created the standard 'Order Entry' database.

It sounds like a Requery action is performed after the update which makes the first record of the requiried data-set the current of your subform.

You need to check your code whether you have recently edited code that has requery action ...

I wish I could say that I was doing something to cause the change. In the last couple of days, it has gone from 'inconvenient' to completely agravating. The original state was that the record selector remained pointing to the order that was just exited. Now it always returns to the first order in a list of orders when a customer has more than one.

For the record, this is essentially the same as the wizard-generated 'Order Entry' database.

This now makes a macro that was developed unworkable. The macro required that when a payment form or invoice (report) was exited, the same order could be recalled (for addtional automated procedures) just by activating the Orders button. Now with the record selector jumping back to the first order, that's not possible.

There don't appear to be any properties in the subform to dictate any action for the record selector. It behaves like this regardless of which button opens another form then returns to the 'Orders by Customer' form.

I don't think I've done anything to write or edit any requery actions.

Help ! ! !

Have you tried Compact and Repair the database?

Are your Windows OS / Access patched / updated with all Service Releases / Service Patches / Updates?

Perhaps, you should post your database (compact then zip to less than 500 KB) and others can have a look ...