Master Form with a condition if subform is available

[peciam]

Hi To all,

Here's the question:

I have a master contract table, it contains information about the contract, years covered, local type ext. I have a field(Yes/No)called teaching assistant in the contract table. I have been tasked with creating a salary table now that would contain salaries for the contracts, linked by local name, salary data will span many years, a one to many relationship.

Should I do it as a subform or a form by itself?

I want to only have the subform available if the teaching assistant field is checked, and also I what the subform closed when I first go into the contract form.

Any help much appreciated!

 

[ChanceD2]

I think it would be easier to have the salary info on a separate form. Have a button that is disabled on the main form (default) and if the teaching assistant field is checked, make the button enabled.

I believe this would be easy and faster.

HTH

C-D2

 

[peciam]

Thanks,

Ok how do make the button disabled until the teaching assistant field is checked?

Also,

with a form popping up what do I need to do to move focus from one to the other? What field on the main form will it return to?

Thanks again!

 

[ChanceD2]

1. Go into design view of the main form and put a button on it. In the properties of that button change the ENABLED option to NO. In the ON CURRENT event, have it check to see if that box is checked. if it is, enable that button.
2. No, you do not need to worry about the set focus. Play with it and you'll see. I'm not sure which field you will return to. Play with it first and we'll cross that bridge later.

HTH

C-D2

 

[ThomasLafferty]

Set the command button's enabled property (Data tab of the property window) to no.

In the AfterUpdate event of the teaching assistant field, use the following code:

     If Me.[!]TeachingAssistant[/!].Value = True 'Checked
          Me.[!]CommandButton[/!].Enabled = False
     Else
          Me.[!]CommandButton[/!].Enabled = True
     End If

Hope this helps.

Tom

Live once die twice; live twice die once.

 

[peciam]

Hi Tom,

I tried your suggestion, I'm gettinga compile error:

Expected: then or Goto

Any idea?

Thanks

 

[peciam]

Hi tom,

Update: I got the code to run, I of course forgot my "then" at the end of the first line.

It seems that I need to be on the teaching assistant field to get your suggestion to work. I want the button to show or not show depending on the check or not check. Is there a way for the form to do that with out having to go to that field?

Thanks

 

[ChanceD2]

I have another idea. How about you leave the button enabled, and have it either open the form or put up a message.

If Me.TeachingAssistant.Value = True Then 'Checked
docmd.openform "FormName"
Else
msgbox "This is not a teaching assistant",,"Error"
End If


PS TO TOM
How do you put the code in the box?

C-D2

 

[ThomasLafferty]

Chance:
I forgot the [!]Then[/!] on my If test!

As Chance suggested, in the OnCurrent event of the form...
Also, if you want this:

I want the button to show or not show depending on the check or not check

Then use this:

Sub frmMasterContract_OnCurrent()
     If Me.TeachingAssistant.Value = True 'Checked
          Me.CommandButton.Visible = False
     Else
          Me.CommandButton.Visible = True
     End If
End Sub

Customized of course for the real names of your form and controls...

Also, if you want to have your code offset in a nifty box for posting in the forum, surround your code like this:

Your routine here

Live once die twice; live twice die once.

 

[peciam]

Interested in any in-sight, suggestions: Please review my question, I stated just adding teacher aide salary data, now user wants to expand the salary data to about 20 different job titles.

Remember I have a master database that contains just contract information: local name, years covered, county, regional office, job titles, etc.

My question is: should I just link to a additional database by local name, remember I need to keep track of several years worth or salary data, contract may spand many years with different salary data for each year. Keep all salary titles in that additional database or?

Thanks to all that reply!