Main form with 3 pages Question

[ramez75]

Hi to all,

I been struggling with this for few hours and cant figure out what am I doing wrong.
I have a Main form which in the detail section I have 3 pages.

My question

On the 1st page I have a date field that i need to link to the date field in the 3rd page but at the same time I need to save the value in the table

Right not this what I have,

Page1 - Date with Control source = dateissued (table=ActionPlan)
Page2 - Control Source =[Forms]![ActionPlan]![dateresponserequired]+30

The problem is I want to save the value in the table=ActionPlan in the field "dateimplemented"

How do I go around that,

Any help is appreciated

Thanks

 

[pbaldy]

This should help (including the caution):

http://allenbrowne.com/casu-14.html

 

[ramez75]

Thank you for the response. I am aware that its better to use queries for calculated fields. But this is the situation I am in and I am open for suggestions if my approach is not efficient.

In the form as I mentioned I have 3 pages as tabs. First page I have a field called "Dateresponserequired" which is usually populated when the record is initiated and the default value is "Date()+30.

Now on the 3rd page there is a field caled "Dateimplementationrequired" which I want to be Dateresponserequired+30days. At the same time I want that value to be saved for historical recoding if I get audited

Thank you

 

[Steve R.]

In my case, I build the due dates based on the date the project is received. I use a table that lists when action is required. Lets call that table tblAction.

For example, I only save the date received. For "ResponseRequired", I would use DLOOKUP to get the 30th day. To get "ImplementationRequired", I would use DLOOKUP to get the 60th day. An additional advantage of using a table to provide the number of days for an action, is that they can be easily changed. For example, if "ImplementationRequired" is changed to 45 days.

 

[ramez75]

In my case, I build the due dates based on the date the project is received. I use a table that lists when action is required. Lets call that table tblAction.

For example, I only save the date received. For "ResponseRequired", I would use DLOOKUP to get the 30th day. To get "ImplementationRequired", I would use DLOOKUP to get the 60th day. An additional advantage of using a table to provide the number of days for an action, is that they can be easily changed. For example, if "ImplementationRequired" is changed to 45 days.

Do you have a sample of your database that you can share

 

[Steve R.]

Too big. Below is an excerpt. Also see attached image.

    Case 1 'Received Received
        Rem The table "deadlinelist is used define deadline time periods to make it easy to change dates.
        Select Case Me.typenum
            Case 1 'Part C project
                DateSpanNum = DLookup("deadlinenum", "deadlinelist", "deadlinepart='partc2'")
                Text80 = DateAdd("d", DateSpanNum, [text2])
                Me.deadlinedate = Text80
                Text96 = DLookup("deadlinetext", "Deadlinelist", "deadlinepart='partc2'") & ". The review deadline is: " & DateAdd("d", DateSpanNum, Me.text2)
            Case 2 'Part D project
                DateSpanNum = DLookup("deadlinenum", "deadlinelist", "deadlinepart='partd1'")
                Text80 = DateAdd("d", DateSpanNum, [text2])
                Text96 = DLookup("deadlinetext", "Deadlinelist", "deadlinepart='partd1'") & ". The review deadline is: " & DateAdd("d", DateSpanNum, Me.text2)
            Case 3 'Part E project
                Rem NO Type E Projects
            Case 4 'Part F project
                DateSpanNum = DLookup("deadlinenum", "deadlinelist", "deadlinepart='partf2'")
                Text80 = DateAdd("d", DateSpanNum, [text2])
                Rem Me.deadlinedate = Me.Text80
                Text96 = DLookup("deadlinetext", "Deadlinelist", "deadlinepart='partf2'") & ". The review deadline is: " & DateAdd("d", DateSpanNum, Me.text2)
            End Select

 

[ramez75]

Thank you for the info, i will give it a try

 

[ramez75]

OK.....I need some recommendation on how to tackle this.

On the same form I want to keep a history of justification of extending the response date.

This what I have and tried but not working like I want so any ideas will be greatly appreciated

On the form (frmActionPlan) the field is called (dateresponserequired = Date()+30). OK this date might change depending on the project if capital is involved or other thing is required, etc.
So I created another field called (extensiondateresponse) with Visible=No. I want a way that when the date is changed then the field "extensiondateresponse" becomes visible and forces the user to type a something that will result in saving the record in tblActionPlan before the date is changed in "dateresponserequired " and when focus is changed then "extensiondateresponse" becomes invisible again.

So far I tried Got Focus and Lost Focus but cant get it to work the way I want.....

Any ideas how to tackle this......Hope I am making sense

Thanks

 

[Steve R.]

On the form (frmActionPlan) the field is called (dateresponserequired = Date()+30). OK this date might change depending on the project if capital is involved or other thing is required, etc.
So I created another field called (extensiondateresponse) with Visible=No. I want a way that when the date is changed then the field "extensiondateresponse" becomes visible and forces the user to type a something that will result in saving the record in tblActionPlan before the date is changed in "dateresponserequired " and when focus is changed then "extensiondateresponse" becomes invisible again.

My understanding of your issue was how best to do: "dateresponserequired = Date()+30", which has been done. As an additional question, you are now incrementally wanting a field for the user to justify an extension deadline. You can do that through a memo field. With that, you need to look at books on Access and search this forum concerning how to accomplish your additional questions.