Ted,

They are not radio buttons and they are not on the form, they are
toolbar buttons. the AZ with Up or down arrows.

Yeah I'm not sure how to do this on the form. The code must be out
there somewhere. Sorry.

=?Utf-8?B?VGVkIE0gSA==?= <TedMH@discussions.microsoft.com> wrote in
news:3A51CA43-F119-4D72-9E47-00AF90637FD9@microsoft.com:

Ok, sorry I did not explain how to enter the instructions into the
VBA code editor.

When you go into any event property, there is a little dropdown menu
that you can open, with the names of all your macros plus an entry
that says [EVENT PROCEDURE]. You select that option, and then click
on the elipsis (...) button on the right side. This will open the
VBA editor, create the evend definition statement
( something like Private Sub button99_Click)  and put the (End Sub)
statement below it. Just paste the two lines
me.orderby = "fieldname"
me.orderbyon = true
in between the two statements that Access created for you. Now you
can reselect the form, ( I usually size the vb editor window to half
the screen and the Access window in the other half) and repeat with
each additional button. When complete, save the code and close the
editor.  

Q

You are VERY close.  Yes, your process was correct.  I suspect that Access
hasn't tumbled to the fact that there is code associated with that frame.  
Here's how to check/fix it.

a) Open the form in design view.
b)  Click on the line that defines the frame box (not the associated frame
label box with the text SortBy in it, but the box that encompasses the option
buttons.)
c) Click on the PROPERTIES button on the menu bar. (alternate method -
right-click on the frame box and then select PROPERTIES from the drop down.
d) Click on the EVENTS tab.
e) Scroll down - find OnClick

At this point there should be
[Event Procedure]
in that line.  Probably isn't.  It is a drop down, so
(f) at far right, click and select [EVENT PROCEDURE]
g) Just to the right you will see a button for this current line only with
"..." - Click it.
It will open the VBA editor positioned to the OnClick event for the frame.  
It should be filled in with your version of my code.

I have seen situations where Access doesn't realize that there is code bound
to an event unless you put it there via this sequence.  Don't know why. So
coming in via this sequence may very well resolve the problem.

If you do NOT have code there, it means that you have an inconsistency in
the name of the control versus the name of the event.  The event proc for the
click event is controlname_Click,  so you should have

Private Sub   frame21_Click()

-----
Click DEBUG on main menu bar.
Click COMPILE to make sure that everything is syntactically correct.

Save, close VBA, close design view and test.

----
While we are at it - if you get to the properties page for a control and
select the ALL tab, and then scroll to the very top line - that's the name of
the control.  You could then change it to 'frame_SortBy'.   Note that this
really should be done before you add code as renaming it will NOT rename the
event SUBs associated with the control.
-------
Another trick:  In the VBA window, at the top of the frame, are two drop
downs.  The left one has GENERAL at the top of the list, and then within the
list are the various controls on the form, sections, the form itself, etc.  
All things that can have code associated.  If you select a control, then the
right dropdown shows all of the possible events for that control.  Those with
code are in bold.  Now a trick - select GGENERAL.  The right drop down will
list any procs (funcions or subroutines) that are NOT associated with a
control, section, etc.  If you see something liike 'fram_21' it means that it
is a proc that isn't associated with a control.  That's perfectly OK as you
can write helper routines to do stuff etc. that you call from whithin events.
But in my example, it is more likely to be a typo in the name of the routine
that needs investigating.

I'll check back in tomorrow and after -it's 9:30PM Friday here.