The code snippent below appears quite complicated, but it's just testing if a control is on the form, if the user has permissions, activates it and sets the focus. For the focus line, look for the orange bit. Just name the control and add .SetFocus. This code runs in the Private Sub Form_Current() procedure of the form. The crazy name for the control is how I handle the multi-language and helps for the form.

Cool. Thanks for sharing!

A final note: I've used .SetFocus a lot, and had a lot of problems within VBA code using it. It tends to throw a lot of different RTEs. Sometimes in a way that isn't very consistent. As with other similar RTEs, I suspect the run-time of VBA ties itself up into a knot and sh!ts itself. On my to-do list is "write a procedure for doing .SetFocus" so that my .accde doesn't just die an ignoble death (even though it ran hundreds of times before without a problem). It seems crazy to have to write new procedures or a bunch of On Error Goto in lots of procedures, but that's what I'm having to do with all the odd RTEs.

I agree. Moving focus around a form is a good way to throw weird random errors. I try to avoid it if possible.