Checkboxes LOCK form Useless

[ortizimo]

I have tried different options and have gone a field at a time. I want the form to be disabled as default then enabled once the Edit button is clicked. Everythig works as it should until I enter a 6th checkbox, then the entire form is locked and buttons don't work. I've deleted the code and the form is still locked. I have Enabled and Unlocked the fields within the Property settings but this just work as that and the code/buttons are useless. Here's what I'm doing:

Private Sub Form_Current()
'main fields
Me.txt_Title.Enabled = False
Me.cmb_Console.Enabled = False
Me.cmb_Condition.Enabled = False
Me.txt_Price.Enabled = False
Me.chk_InCollection.Enabled = False
Me.chk_Wishlist.Enabled = False
Me.chk_Favorite.Enabled = False
Me.chk_Rare.Enabled = False
Me.txt_Remarks.Enabled = False
Me.chk_Disc.Enabled = False
Me.chk_Cartridge.Enabled = False <---this is the one that starts it all...the 6th checkbox locks everything up

'Bottom buttons
Me.cmd_New.Enabled = True
Me.cmd_Save.Enabled = False
Me.cmd_Cancel.Enabled = False
Me.cmd_Edit.Enabled = True
Me.cmd_Delete.Enabled = True
Me.cmd_Exit.Enabled = True
End Sub

I have also used the following and get the same results:

Private Sub Form_Current()
Dim ctrl As Control

'Lock all textboxes
For Each ctrl In Me.Controls
If TypeOf ctrl Is TextBox Then
ctrl.Locked = True
End If
Next



'Lock all checkboxes
For Each ctrl In Me.Controls
If TypeOf ctrl Is CheckBox Then
ctrl.Locked = True
End If
Next

'Lock all drop-down menus
For Each ctrl In Me.Controls
If TypeOf ctrl Is ComboBox Then
ctrl.Locked = True
End If
Next

'Bottom buttons
Me.cmd_New.Enabled = True
Me.cmd_Save.Enabled = False
Me.cmd_Cancel.Enabled = False
Me.cmd_Edit.Enabled = True
End Sub

Either will lock the form useless even when no code is in it at all, and I have to start from scratch just to end up here.

[June7]

Please post code within CODE tags to retain indentation and readability.

Other than simplifying code so there is only 1 loop through all controls, don't see anything wrong.

For Each ctrl In Me.Controls
    If TypeOf ctrl Is TextBox Or TypeOf ctrl Is CheckBox Or TypeOf ctrl Is ComboBox Then ctrl.Locked = True
Next

But that will probably still cause the lockup issue.

I am not able to replicate issue. If you want to provide db for analysis, follow instructions at bottom of my post.

[Micron]

much easier to set Allow Edits, Allow Additions and Allow Deletions to false, or alter the recordsettype property?
I also can't see any issue, notwithstanding that there's much code for this. Perhaps the problem control has code associated with it, but I cannot think of an event that would fire by being disabled.

[Micron]

Please post code within CODE tags to retain indentation and readability.

FYI - You have asked this person to do that at least once before.

[ortizimo]

DB for Analysis

retrogamesDB.zip

[June7]

Instead of repeating the control code, put it in its own Sub and call that Sub in each event procedure as needed.

Private Sub SetControls(booEnable As Boolean)
Dim ctrl As Control
    For Each ctrl In Me.Controls
        If ctrl.ControlType = acTextBox Or ctrl.ControlType = acComboBox Or ctrl.ControlType = acCheckBox Then
            With ctrl
                .Enabled = booEnable
            End With
        End If
    Next
End Sub

Move DoCmd.GoToRecord , , acNewRec to end of procedure

Private Sub cmd_New_click()
    SetControls (True)
    DoCmd.GoToRecord , , acNewRec
End Sub

Private Sub Form_Load()
    DoCmd.SetOrderBy "Consoles, ASC, title, ASC"
    SetControls (False)
End Sub

There are only 4 checkboxes on form.

I set breakpoint in Current event code it never executes. I generally avoid Split form but have used it twice for very simple, very small db.

Still can't explain why New button is not enabled when form opens.

[Micron]

It is a split form, and you put all your buttons in the detail section. No can do (well you did, but not much will work).
You will have to select all, cut, and paste in footer (or header) and reconnect all of the events one by one.

After doing so, it is very unstable. If I 'edit' I can use navigation controls to move from record to record, 'editing' as I go and detail record becomes the current record (in the bottom) and top view is enabled. Click on another record in the bottom and it crashes every time.

You can try compact/repair or decompile switch on open on your db, but I'd say I'm not surprised by the result. A split form is supposed to be provide 2 views of the same data - single and datasheet. Each view is comprised of the same fields. It would seem Access doesn't like it if you select a locked datasheet record while the 'single view' record is enabled. When you think of it, there's no way you could do that in a single form view (select the next record while maintaining the view of the current one, especially with one locked and the other not) so maybe that's why the crash every time.

If it works for you after fixing the control positions I'd sure like to know.

[June7]

Okay, moving button into header section makes a big difference. And now the Current event runs.

I simply dragged button into header section and code works.

Current event runs after button click event so the controls are not available after clicking New button. I removed code from Current event.

I am not getting the crash.

Frankly, I really don't see any benefit to disabling all data controls.

[ortizimo]

Okay, moving button into header section makes a big difference. And now the Current event runs.

I simply dragged button into header section and code works.

Current event runs after button click event so the controls are not available after clicking New button. I removed code from Current event.

I am not getting the crash.

Frankly, I really don't see any benefit to disabling all data controls.

Copy...thank you all for your great help and explanations. I will do the changes and reply if I get it to work. FYI, I like having some buttons disabled until I need them due to human error. I understand is not a normal thing to do but with my Access 2003 everything worked as I need it. Now with 2016 version all became locked. Again thank you all as I continue learning.

UPDATE:
Well after working around with the suggestions in this post I found out that having the split-form is a no-go for Access 2016 (Micron). I will have to re-install my old copy of 2003 and see why it works there and not in this new version of Access. Thanks again!

[Micron]

I am not getting the crash.

you replicated my actions: navigating, unlocking (edit click) then selecting a locked one from the datasheet and no crash?

[ortizimo]

i still get the crash but found out it was the split-form doing the hold-up/lock. in 2003 works fine (old db)...in 2016 split is no-go. will investigate further once I re-install 2003 in a VM tonight. thnx

[June7]

@Micron, tried that and still no crash. After clicking Edit, the datasheet is not locked so no problem selecting another record, which is then locked by Current code.

I do wonder how the 2003 version works because having code in Current event interferes with New Record.

Also, acCmdSave is wrong command, should be acCmdSaveRecord. Maybe better to use Dirty. Review http://allenbrowne.com/bug-01.html

[Micron]

if datasheet isn't locked, then I'm not surprised it didn't crash, and if it didn't lock the datasheet, is that because your alterations were different than mine or is it a version thing?
I'm not really looking for an answer because this isn't something I'll ever do.

[June7]

Can't say. Code to set controls is still called from same events.

I have also never done to this degree. I have locked some controls that should not be available until another control has input. I have also locked/hidden buttons until they are relevant to the process.

[irish634]

I have tried different options and have gone a field at a time. I want the form to be disabled as default then enabled once the Edit button is clicked.

Why don't you just toggle the 'AllowEdits' and 'AllowDeletions' properties on the form?

In design mode, set the form properties:
AllowAdditions = True
AllowEdits = False
AllowDeletions = False

Then just toggle them:

If you have an 'edit' button do something like this:

Private Sub cmd_Edit_Click()

    Me.AllowEdits = True
    Me.AllowDeletions = True
    
End Sub

Then when you click a 'save' button do the opposite:

Private Sub cmd_Save_Click()

    Me.AllowEdits = False
    Me.AllowDeletions = False
    
End Sub

It just seems to me you are going through an awful lot of programming when this may suffice...