Yes easy (?:).
More than one way to do it.
If you click on wizard buttons (buttonset1) in your build form and check properties sheet you'll see that its properties read :
Class : txtbtns (or picbtns, vertxtbtns if you have use other types)
Classlib : home()+'wizards\wizbtns.vcx' (where home expanded as real path)

This means buttons are from wizbtns.vcx (located at home()+'wizards\'. Take the easy path for the moment. Copy wizbtns.vc* to a new path and filename, say :

c:\myclasses\mymodifiedbuttons.vc*

Then a little hacking for your already build form would use this new one which you're going to fiddle with. In command window :

close all
use myform.scx
replace classloc with ;
   'c:\myclasses\mymodifiedbuttons.vcx' ;
   for atc('wizbtns',classloc)>0
use

Now your form is using your copy. You can play with it since original class code is intact. To test do this :

modi class txtbtns of 'c:\myclasses\mymodifiedbuttons.vcx'
Dblclick on 'Next' commandbutton to get its click code window and add code :
wait window nowait 'Modified version is running'

Save and run your form. As you click next you would see the wait window message.

Other ways are more complex for the moment I think.
However don't undertake my original reply. It's dangerous to store recno() in a buffered table. Till table is updated you have a teporary recno() for new records (with negative value). They always start from -1 and in each append session. This means if you were updating (save updates) per record you'd be saving always -1 to the field.

Cetin

>OK, I see it now.
>So you suggest I do not fiddle with the 'real thing', somehow I can copy this class into one of my own and work from there? Is this easy to do?
>
>,
>>-In command window :
>>modi class txtbtns of home()+'wizards\wizstyle'
>>
>>-Two windows come up, one titled 'Class designer - ...' and other 'Properties ...'
>>
>>-If 'proerties' window doesn't show up select Properties from View menu.
>>-Rest as I told before
>>Cetin