Duplicate events on access form (access 2003)

[eyalco]

I have a receipt form (with continuous sub-form) where I need to issue many receipts in 1 form (from 12 to 36).
I need to duplicate the details of each receipt (the only change every time is the date and the cheque number).
For the duplication i'm using :

Me.dup_field.DefaultValue = """" & Me.dup_field & """"

for the cheque number i'm using :

Me.CHECK_NO.DefaultValue = """" & Me.CHECK_NO + 1 & """"

My problem is the date : each cheque is for the following month - how do I use the dateadd function along with my code to aachieve what I need please?

[NeoPa]

In which of the forms are the controls :
Me.dup_field
Me.CHECK_NO

"the following month" refers to the month following which? The current month, or the month associated with the previous record?

What and where is the control that holds your month date?

[eyalco]

dup_field (which is the date).
The following refers to the first month I write: 1st cheque I write and then I wamt the following cheque to be written (cheque are givven in a 1 month interval so if I write 01/09/09 the next will be 01/10/09).
Thanks.

[NeoPa]

I'm not sure whether that answers any of the 4 questions posted.

Please try to answer each of the questions so I can try to help.

[eyalco]

The controls are in the sub-form (continuous).

the following month" refers to the month following which? The current month, or the month associated with the previous record?

The month associated with the previous - It's on 1 month intervals of the 1st date entered.
example : If cheque is due on the 15/09/09, then I should get automatically the in next line - 15/10/09.

The control that holds my month date is called "payment_du e" and it's in the sub continuous form of the receipt (called "sub_receip t).
Thanks

[NeoPa]

I'm not sure where you're putting the code (listed in the Original Post), but if it's working that's great.

The first line should be straightforward enough as the value never changes. Furthermore, using the .Default property is certainly the best way to do this.

If you have the second line shown in a place where it works correctly (possibly the After_Update of the control itself), then that's also good thinking and should work (You probably already know that it does).

Getting onto the date issue then, now I realise this is simply a date manipulation issue and you already have the most complicated issues covered :
In code similar to what you are already using for your Cheque Number control :

Me.Payment_Due.DefaultValue = Format(DateAdd("m", 1, Me.Payment_Due), "d mmm yyyy")

It is important to check that the current entered value is a valid date however.

PS. Your date format can be anything that suits you. I've used an internationally independent version here.

[eyalco]

Thanks, I think I have a problem with the date format either in the "payment_type"c ontrol or with my access/computer.
When I type 01/09/09 the next date I get (in the next line) is 30/12/1899 instead of 01/10/09 and it stays that way on the next rows.
The date format on the control is short date.
Thanks.

[FishVal]

Problem with DateAdd and Default Value

[eyalco]

Thanks, That's great - exactly my problem.
Thanks.

[NeoPa]

My bad.

Of course the .Default value would be clearer with the "#" characters around it. That is to say they can work without (in some circumstances only) yet they should always work with. I should have used them, unquestionably.

I would also add that using any format of date that could be ambiguous (dd/mm/yy and mm/dd/yy ARE ambiguous) is open to problems. Three character months are useful for clarity I find.