Navigation Buttons 1

[ramondrumon]

All the ways I have seen so far to make incremental numbers can eventually be different than the navigation button number on the bottom of the form. I am afraid this will confuse the end user. This number always seems to be accurate, is there any way to use this number in our form, then they would always be in sync with each other. Is there a number guru out there?

 

[gusbrunston]

Hi:

You'll find an interesting discussion of this subject in the following thread: thread702-375516

I happen to agree with MichaelRed that the incremental numbers which will change with every sort and filter, are generally useless to me in my applications. However, there may be others uses beyond my experience...but we wouldn't want to revert to the ancient times before relational databases, would we.

e.g.,
I have a table, "tblTransactions", with thousands records. Each record has a unique ID number, the Primary Key (not autonumber) which I can reference from combo boxes, text boxes, etc., much easier than by trying to calculate how many hundreds and tens of records to go backwards or forward. (And if I wanted to to that, I could use the built-in navigation buttons.)

If you want to avoid confusing the end user, then hide the navigation buttons. Gus Brunston An old PICKer, using Access2000.

 

[LittleSmudge]

If you want to avoid confusing the end user, then hide the navigation buttons.

OR Simply hide the Id Index number. It conveys NO additional information that the user needs so WHY put it on the form ?



G LS
accessaceNOJUNK@valleyalley.co.uk
Remove the NOJUNK to use.

Please remember to give helpful posts the stars they deserve!
This makes the post more visible to others in need! :-D

 

[ramondrumon]

Thanks for the replys. I guess I will hide the built-in buttons, it just seems a waste because the buttons take up no room and work well. I don't quite understand about your unique ID number, Gus. Did you use DMax or what did you do exactly, it sounds like what I am looking for.

 

[gusbrunston]

Hi:

In a form for entering new clients (property owners) I put the following in the property sheet for the control bound to fldOwnerID:

Data > Default Value > =

=DMax("[fldOwnerID]","tblOwners")+1

If the highest previous fldOwnerID is 908, then the default for the new owner is 909.

Hope this helps. Gus Brunston An old PICKer, using Access2000.