Reply The command or action SAVE RECORD is not available now

[phxbypdx]

I understand that the form has to change in order for this event to be available.

I have a hidden checkbox named wasRead, with a Control Source of (appropriately!) wasRead. It's a simple boolean field to see if this line item was read.

in the message_dblClick event, I have the following code:

Me.wasRead.Value = 1
    If Me.Dirty Then
        Me.SetFocus
        DoCmd.RunCommand acCmdSaveRecord
    End If
    DoCmd.OpenForm "frmChat", acNormal, , , , acDialog, lineID

The original value of wasRead is 0 (seen with breakpoint)... so I know the value is changing. Also, me.dirty = true, because I get into the If statement.

What gives?

Scott

 

[boblarson]

1. get rid of the docmd

2. use

    If Me.Dirty Then Me.Dirty = False

Not sure about why you had the Me.SetFocus part in there but you could put it in afterwards if necessary.

Also, make sure your underlying recordsource is updateable. If it isn't then you will get that error message.

 

[phxbypdx]

Yeah I pulled a stupid here. It's bound to an underlying recordset, so I don't need to even worry about running the saverecord. Do I need to use the if me.dirty then me.dirty = false? what's the purpose behind that? As soon as I execute this code, I pop open a new form which, when closed, requeries this original form (and that record is now removed from display, as a filter resides on the form "where wasread = false"

The setfocus was there because, as I was researching this, somebody mentioned that the form needed to have focus. Don't need it.

Thx bob

Scott

 

[boblarson]

The

If Me.Dirty Then Me.Dirty False

forces a save of the record IF anything has changed. If nothing has changed (form isn't dirty) then it won't try to save.


and this code

DoCmd.RunCommand acCmdSaveRecord

always attempts a save regardless if something has changed.