I don't think that will happen, you can tab to input capable fields. Phil ****** You might consider changing the fields into Both (input and output) with attribute PR (protect). Thus creating a input fields where they should be able to tab to, without the possibility to change the information. Rudolf ========================================================= If you change the 'O'utput fields to 'B'oth fields to enable TAB, in addition to DSPATR(PR) for those fields, you might want to specify CHGINPDFT also. Because the fields are now input-capable, you'll be able to TAB through them. Because the fields are 'protected', your users can't type into those fields. And CHGINPDFT with no parameters will remove the underline from the fields, making them look like they're not input fields at all. The program(s) will need to be recompiled because the input buffers will be changed when your ouput fields become input-capable. But they'll be protected, so the values shouldn't change. Tom

I don't think that will happen, you can tab to input capable fields. Phil ****** You might consider changing the fields into Both (input and output) with attribute PR (protect). Thus creating a input fields where they should be able to tab to, without the possibility to change the information. Rudolf ========================================================= If you change the 'O'utput fields to 'B'oth fields to enable TAB, in addition to DSPATR(PR) for those fields, you might want to specify CHGINPDFT also. Because the fields are now input-capable, you'll be able to TAB through them. Because the fields are 'protected', your users can't type into those fields. And CHGINPDFT with no parameters will remove the underline from the fields, making them look like they're not input fields at all. The program(s) will need to be recompiled because the input buffers will be changed when your ouput fields become input-capable. But they'll be protected, so the values shouldn't change. Tom