If IsNull CustomerID Then Disable Subform

[burrina]

I am trying to prevent users from entering a order without the correct fields filled in such as CustomerID.
Here is my criteria; These fields must be filled in! CompanyOrderSubform is the name of the subform. Main form is named CompanySellInventory
Company
Customer
Employee
Shipping Method


SubmittedBy
OrderDate
PurchaseOrderNumber

Here is what I tried with no luck.
If IsNull([CustomerID]) Then
Me.CompanyOrderSubform.Enabled = False
Else
If IsNull([EmployeeID]) Then
Me.CompanyOrderSubform.Enabled = False
Else
If IsNull([OrderDate]) Then
Me.CompanyOrderSubform.Enabled = False
If IsNull([PurchaseOrderNumber]) Then
Me.CompanyOrderSubform.Enabled = False
End If

Of course my idea here is to disable the subform until the fields have been properly filled in.

[Rawb]

The easiest thing to do is move the Subform out into its own Form. Then have a "Create Order" button that doesn't open the new Form unless all the criteria has been entered.

[alansidman]

I would do it in reverse. In the Current Event, disable the subform or hide it. Then if all the fields are not null, make the subform enabled or visible. I would add a command button to open the subform. If the main form items are not completed then, a message that the subform cannot be opened until all fields are completed.

Alan

edit: or as Rawb described, use a separate form. But open it with a command button as we have both indicated.

[burrina]

If Me.Check176 = True Then 'Displays Products Form if Criteria is met.
[OrderDetailsSubform].Visible = True
Else
[OrderDetailsSubform].Visible = False
End If
End If

Why does this not work? Checkbox is named Check176 and Label is named Active
Subform is named OrderDetailsSubform off main form OrderDetails
Code run on OnCurrentEvent procedure.

Ok, I deleted the Label and named the Checkbox Active still no luck.Here is screenshot

[alansidman]

I think that the issue is with your naming convention for the subform.

Look at this link on subforms and referring to them.

BTW: It is not good practice to name controls Check176. Six months from now you or someone else is doing some design updates. What will that mean to them. Give your controls names that will help you to follow what is going on in your code.

Look at this link on naming conventions

http://www.dhdurso.org/articles/acce...onventions.pdf

In the long run, you will be happier if you follow a naming convention. I have gone back to db I built five years ago when I first started and its a real issue trying to figure out what I did in a couple of situations.

[burrina]

Thanks for the help. However, I renamed the form to frmOrderDetailsSubform and the code still does not work.

[burrina]

This solved the Problem. I know my db could use some restructuring but naming convention was not the problem. I will in the future be more careful with this though.

Me.[Order Details Subform].[Form].Visible = False worked like a charm.

[alansidman]

Glad you solved it. I apparantly did not attach the link that I thought I had on referencing sub forms. Just for future information.

http://www.datapigtechnologies.com/f.../subform2.html

but you got it Burrina. Nice show of figuring it out.