I won't assume whether you should or shouldn't do this, but the correct answer is going to use the DateAdd function.
If you are planning to update the current record, perhaps because you are updating some sort of "next visit due" field or a "data expires after" field, the code behind a form involves at least two or three decisions.
1. Where to put it? You have to decide what needs to be done in order to indicate that this update should occur. Normally, I use a command button and put the code behind an OnClick routine. The command button wizard DOES include an option to initiate a record update, so you could start by building a Record Update button through the wizard, then add your options to the code.
2. Do you want to add one month, 30 days, 4 weeks, or some other specific amount? (This contributes to which option you would use in the DateAdd function.)
3. Is this really an update or do you want to write a new record? Makes a difference in the function you choose in the button wizard.
The other way to do this is with recordsets. If you are creating a new record and still want to see the current record on your form, it is possible that recordset operations might be the only way to do what you want. If you are not familiar with VBA, any explanation I give you would be over your head. So I won't go in that direction for the moment.
