Lebans navigation buttons

[Pason]

First off let me say thanks to Stephen for providing these custom
navigation buttons. I'm new to access and it has been a big help.

I'm having a problem creating new records using these buttons and I'm
wondering if it's me or the code and whether anyone has a solution.

These buttons can be found on Stephen's page at
http://www.lebans.com/recnavbuttons.htm.

Open the form 'frmSampleRecordNavigation' and add a new record. Begin
typing the customer name - The access buttons become enabled so that you
can add another record while the custom buttons do not. I have a
situation where the user will need to add a large number of records one
after the other so this is undesirable.

Thanks for any help you can provide,

 

[ruralguy via AccessMonster.com]

I made some small changes to Stephan's code. If you send your addy to Rural
Guy at Wild Blue dot Net, I'll send it to you.

 

[ruralguy via AccessMonster.com]

Unless you know a good file hosting service where I can upload it, If so,
then just post the service and I'll post when it is uploaded.

I made some small changes to Stephan's code. If you send your addy to Rural
Guy at Wild Blue dot Net, I'll send it to you.

First off let me say thanks to Stephen for providing these custom
navigation buttons. I'm new to access and it has been a big help.

[quoted text clipped - 12 lines]

Thanks for any help you can provide,

 

[Pason]

Thanks that's a nice improvement.
Here's the file for anyone else who's interested:
http://www3.telus.net/jlh140/LebansNavButtons.mdb

I'm still having a few problems. If you have any tips on where to begin
I'd appreciate it.
When the Nav Buttons are on a subform (themselves also being a subform)
and you change records on the main form, the subform records always say
"1 of 1" until you advance. I hope that made sense.

Also if you add a new record, start typing in a field, add another
record, start typing and then try to go back to the previous new record
it doesn't work.

How do people usually handle this sort of thing? The access buttons
seem very limiting always being at the bottom. With sub-sub-forms it
gets very confusing very fast. Is Access not the right tool?

 

[ruralguy via AccessMonster.com]

Hi Jonathan,

I didn't completely wring out the software after I made the changes. There
may be other areas that do not work correctly. I did it mostly to give you
some assistance in making changes to Stephan's code and get you started. It
might be wise to just stay with either the native Access Nav buttons or
Stephan's NavButtons unmodified.

Access works for lots of people but whether it is the right tool for you will
have to be your call.

RG

 

[Van T. Dinh]

I haven't looked into Stephen's sample carefully so the modification may
create some other problems but the following seems to work:

You can use the Form_Dirty Event of the Form [frmSampleRecordNavigation] to
enable the cmdNew button. The code I use:

========
Private Sub Form_Dirty(Cancel As Integer)
Me.SFfrmNavButtons.Form.cmdNew.Enabled = True
End Sub
========

You need to add error-trapping code and my recommendation is to check /
validate the data in the Form_BeforeUpdate Event also to make sure that the
Record can be saved into the Table.