Next record Triangle button when held down wont run through records in 2010 as it did in 2000

[DBenz]

Hi,
My dbase I have always been able to hold down the next record forwards or next record backwards triangle marked button at foot of Form and see the records rolled though one by one then let go as I see the one I want appear. This did such in Access 2000. Win XP 32bit

I now open this dbase into Access 2010 on a win7 64bit PC (installed as 32bit as is correct advice from Msoft and the vendor) but that function doesnt work, I have to click 1295 times to scroll through 1295 records, as I search on the records visually, the dbase displays bmp images (clever eh ! ) so I could always spot the one I wanted flash past.

This is prohibitive.

What has Msoft done to this useful feature ?

DBenz

[June7]

I never heard of this feature - using Access since A2003. Would be nice if it worked.

[DBenz]

Hi,
I just typed out a reply, hit 'reply to this thread', and it vanished.
lets try again.

I have just opened the dbase on my laptop running XP and access 2000 and I am able to scroll through my records holding the next record button down, the one with the black triangle on it at foot of form.
THIS FEATURE WORKED AS I HAVE JUST CONFIRMED, IN ACCESS 2000, SOMEONE HAS MESSED IT UP SINCE THEN. Why remove the ability to scroll through records.

I cannot go click click click 1295 times, its a pictorial dbase and I need to roll through the records.

I cannot go back to access 2000, I am now win7 and just paid £450 to get hold of access 2010 for a win7 OS. and I wont be going for office 2013, as thats a rip off meaning buying office pro TWICE, ONCE FOR TOWER AND ONCE FOR LAPTOP, JUST WHO WANTS TO PAY A VAST AMOUNT OF MONEY TWICE. so I need this fixing in 2010.

damn them, why cant they leave things working as they were. They have stopped me accessing my dbase as I need to.

I NEED SOMEONE TO FIX THIS ISSUE SO I CAN ACCESS MY DBASE..ITS CRAZY I MOVE FWD TO 2010 AND ITS KILLED MY DBASE ACCESS METHOD.

Coding I guess that identifies button held down and moves fwd until button released..this has to be feasible.

Could someone from the Access development team explain why that was done and how to fix it ? Write the coding that fixes it etc.

I google this and there are others also complaining about its loss.

Note I am searching visually, I am not able to enter criteria, or filter or other such stuff. Its also for when searches fail and I resort to a visual find.

http://www.pcreview.co.uk/forums/do-...-t3055269.html

http://windowssecrets.com/forums/sho...in-Access-2007

DBenz.

[DBenz]

Hi

THIS IS A BIG CRY FOR HELP FOR ALL THOSE THAT USED TO SCROLL THROUGH RECORDS.
Form view.
Access 2000 scrolled through records when next record button at foot of form clicked on and held down , likewise went backwards if previous record button held down.
Msoft in access 2007 and thereafter have deliberately disabled Mouse scroll wheel from record scrolling, but somehow managed to wreck the button hold down method which wasnt an issue and not part of the plan.

However they havent fixed it, cant be bothered it is said, so there is no way of scrolling records with mouse on those two buttons at foot of form view.

TO HAVE SCROLL RECORDS DISABLED IS CRIPPLING, clicking the next record button thousands of times is not practical.

Page up and page down is suggested, but if your form is tall enough to have a scroll bar at right, page down ceases to work and you cant scroll forwards through records.

How a dbase can lose its record scrolling is crazy. I just cant believe this is so, though considering the mess win7 is compared to XP maybe I can.

Mine features images in form view, and I must view it in form view, I am scrolling looking for a certain image. scrolling is vital to me.

As humans created the scroll ability for the buttons, then uncoded it, they can surely re-code it...and you guys are more intelligent than Msoft !

Can someone do that please or code some alternative that works with forms that have scroll bars at side and sub-forms within.

DBenz

[June7]

This website is not affiliated with Microsoft so can't answer for them.
I have never seen this need expressed before and never seen any code to accommodate.

My mouse scroll wheel works although on a form with thousands of records, really doesn't help a visual search because the records go by too fast.

[MatthewGrace]

I'm kinda new. I wanted to see if it was possible with my meager knowledge of code to make a workaround for you (and of course, to build my own skills in the process). I made a form with nothing significant on it and 40 records. It uses buttons that, upon toggling, run forwards or backwards through the records.

The bad: If you go past the last record or before the first, you will surely error. I was making a catch for this, but alas failed due to fatigue. Well, the "error" just causes you to press End, nothing else harmful to my knowledge, so it's a tiny nuisance but still not pro. There are other small things I feel I could have done to improve the feel of this.

The good: there's a nifty flip-speed combobox so you can adjust the speed at which you browse. It's editable so you can come up with your own speed if you just "Edit List Items"
All in all... I'm new, and I hope you can make it work. I did learn a little while making it. its quite simple code and the naming conventions are very straightforward. Maybe plug in the names of your own buttons and some copy/paste work, it may serve you as a poor-man's substitute for what you're going for.
Flip Records Automaticaly.accdb

code:


Form:

[DBenz]

Hi MathewGrace,
Before I reply, I see that a new post I made to the programming section has in fact ended up as a reply to the post I made in the access general section, that post is no longer there and has moved to programming, though I had hoped to have the coding request subject title as a new eye catching request. How become these have fused together and switched pigeon holes ?

As for the code you have done, many thanks indeed, you are a star :-)
I will need to know how do I go about putting the two buttons and the record browse rate window into my form.
What do I do with the .accdb file or link
How do I then apply the code ? I have never used code before.
I like the idea of indicating how fast the records scroll past, that's excellent and will be invaluable, some good might actually come from the loss that is Msofts doing. Still cant believe they kill of scrolling and cant be bothered to fix it.

This is in fact of great use to not just me but anyone wishing to scroll their dbase and should be pinned !

June7, having scroll wheel scroll records is no use if the form has a scroll vertical bar at right, as mine has, as all it does is scroll to base of record and stop.
Msoft wanted to kill that function off, did so and also inadvertently killed the correct way, holding down next record button.
<<I have never seen this need expressed before>>
see links I gave to others also missing an ability to scroll records on form view. Access2000 users had this ability. I cant see how users would want to go click click click thousands of times though.

DBenz

[Missinglinq]

Sorry, but the 'auto-repeat' feature of the native Navigation buttons disappeared with v2007, and per Allen Browne, the bug has never been fixed by the Boys of Redmond! Nor does Allen give a workaround.

Linq ;0)>

[MatthewGrace]

For the sake of curiosity I have tried again and made some improvements, including not erroring on the beginning or end of the file. It works well on my machine, but I'm FAR from a good programmer. I'm sure there are many more efficient ways to do this, but feel free to take my version and try and implement it.

You said you're not familiar with code, which makes that really tough I'm not sure how much help I can be. What I would try is this:
1) Open the Form you'd like to flip through in Design view and in the Properties panel (toggle with F4), look for the tab named "Other". There should be a property called "Has Module". Click and select "Yes".
2) Press Alt+F11 simultaneously which will open the code window. in the upper left you'll open the hierarchy to open "Form_whateveryourformsnameis"
3) You'll have to copy/paste all the code in there. You can retrieve that code by following the same steps above only on my DB. Get my newest test: Flip New.accdb
4) Next, you'll need to have the 3 controls I created at the top (the 2 buttons and the combobox speed control). Again, I think it would be best to open both your database and mine at the same time, and simply highlight my 3 controls, copy them, and paste them onto your form in your database.

*I think putting them in the header is the cleanest way in this case. If you don't have a header you can go into design view, rightclick on the form somewhere and in that popup should be "Form Header"

you can then rightclick in the header and paste all the controls in there if you like. adjust back color by again right clicking on the header form and looking for that option.

I hope it goes well. Take care

[June7]

I agree that removing this feature was an unfortunate move by Microsoft, although I don't remember it (didn't use A2003 very long) and never really had a need for it.

I merged your two threads because they were on the same topic and because Matthew had replied to the original. I could have deleted the duplicate.

A superior effort by Matthew, certainly deserving of elevation to status beyond 'Advanced Beginner'.

I hope it serves as a reasonable substitute. If you prefer, the buttons could be in the form footer.

[Missinglinq]

...I agree that removing this feature was an unfortunate move by Microsoft, although I don't remember it (didn't use A2003 very long) and never really had a need for it...

I suspect that few people did, which was probably why it was removed! And to be honest, I can't really imagine clicking a button down and holding it long enough to cycle through the aforementioned 1295 Records! I would think another method of navigation would be preferred, such as a Combobox or a search field/button. If the Form in question is a Datasheet View Form you could change it to Continuous, put the search apparatus in the Header and tweak the Form to look like a Datasheet.

Linq ;0)>

[June7]

It's just annoying that MS has practice of removing a working feature even though people appreciate it. Why break something that works? Examples:

2013 drops pivot table/chart and Collect Data

Office 2010 completely removed support for dBase (something I did find useful).

[Missinglinq]

Of course, it may not have been intentional! Access is a hugely complex program, despite the idiots that consider it to be a 'dilettante's program,' and we all know how easy it is to change 'one little thing,' and suddenly nothing works! But of the 25-30 'old-things-that-no-longer-work' that Allen Browne identified (and I'm sure reported) with v2007, they've only fixed about 15 or so; I figure they don't fix those that were done on purpose! And, to be fair (and I hate having to be fair, when criticizing the Redmond Boys!) they have to look at what the majority of the Access community are using. The one thing that absolutely plucks my last nerve is their habit of having to move everything around; if you run v2007 you cannot, with confidence, tell someone where to find a certain feature/property in v2010 or v2013! Of course, the same applies to Windows 7 and Windows 8!

Ugh! No, Double-Ugh!

(Oops! Did I say that out loud?)

Linq ;0)>