Record Navigation Problems

[percivalsangel4]

I made a form in single form view with a 'Request Number' as a field. The 'Request Number' is linked to a subform that is in datasheet view. When I want to go to the next record, the form will first scroll through all the records in the datasheet, before going to the next 'Request Number'. I want the form records to navigate by 'Request Number' only.

If this makes sense, I was wondering if any one could give me any suggestions. Thank You!

 

[edtab]

That behavior sounds unusual; please post your stripped down db so interested parties could look into it.

 

[RuralGuy]

Are you using the nav buttons and are they on the MainForm or SubForm?

 

[percivalsangel4]

I tried both nav buttons. The nav buttons on the datasheet subform control only those records. The nav buttons on the main form wont change the 'request number' until it goes through all records on the datasheet subform. I even created my own nav buttons. Didn't work. I'm thinking that a link is wrong or missing or a VB expression needs to be added some where, but I'm at a loss. I've tried all that I know which is very little.

 

[RuralGuy]

Something weird is going on. As edtab said, can you post a stripped down version of your db so we can look at it? Remove any sensitive data and Compact and Repair before you zip it. The file need to be < 394KB to post.

 

[percivalsangel4]

Uploaded Database

Hope this worked, Thank You!

 

[RuralGuy]

There is no sample data to demonstrate the problem. Which form are you having problems with?

 

[percivalsangel4]

The Tab Subform 'All'. I removed all test data upon compact and repairing.
Enter 1 in Request No., then enter multiple supplies. Create a new record. Then Enter 2 in Request No., then enter multiple supplies. Repeat however many times you would like. Then you should see my problem when you try to navigate the records.

 

[edtab]

The recordsource of your Tab "All" is a query. This may be the problem.
I changed the recordsource to the table itself and it worked flawlessly.
Please try it that way and post back .

 

[percivalsangel4]

I need to ask why I've been trained to link my forms to queries I was never really clear on that. But I've figured it out with the help of a co-worker of mine. I will post an updated finished version and will also post the explaination as to why I link forms to queries cuz again im not sure, its just how I've been trained.

 

[RuralGuy]

Queries are far more powerful and flexable than tables and if you ever switch your BackEnd to SQL Server than you will need to have everything in queries. A form can *not* tell the difference between a table and a query and a query of a single table should always work.

 

[percivalsangel4]

We use queries instead of tables for our forms because we have multiple users. Our databases are all on a server. By using tables it will lock up all records and not allow for multiple user access. I was told that using queries clears this up.