Undgå postskift

Er ikke helt klar over hvad du vil. Men du kan gennemtvinge en lagring med denne:

DoCmd.Save

DoCmd.DoMenuItem acFormBar, acRecordsMenu, acSaveRecord, , acMenuVer70

moving to another record forces the beforeUpdate event and if you dont want to go to another record then you need to save the record another way.

If you place a button on your form using the button wizard you will see that you can choose Record Operations + Save Records which actually makes the code for you.

You could also ask if the user really doeas want to save the record first.

Private Sub Command8_Click()
On Error GoTo Err_Command8_Click

If MsgBox("Save? ....", vbQuestion + vbYesNo) = vbYes Then

    DoCmd.DoMenuItem acFormBar, acRecordsMenu, acSaveRecord, , acMenuVer70
   
End If

Exit_Command8_Click:
    Exit Sub

Err_Command8_Click:
    MsgBox Err.Description
    Resume Exit_Command8_Click
   
End Sub

Findes der ikke en måde hvorpå man kan annullere et movenext/moveprevious selvom man klikker på en af navigationsknapperne movenext/moveprevious.

If MsgBox("Save? ....", vbQuestion + vbYesNo) = vbNo Then
   
        Cancel = True
       
    End If

THat was in the before update event

Private Sub Form_BeforeUpdate(Cancel As Integer)

If MsgBox("Save? ....", vbQuestion + vbYesNo) = vbNo Then
   
        Cancel = True
       
    End If
End Sub

Lav dine egne navigationsknapper!~)

and if you add
Me.Undo

AFTER Cancel = True you undo all changes

It isnt logical to use the navigation buttons which are used to navigate through records, to update (save) the current record!

If you made your own navigation buttons as såg suggestions, and you used the button wizard to make these, then they would still give you code which would navigate through the records.

You could modigy the code but in the end you would either use code similar to 08/04-2007 17:26:07
or code which moves to the next record to force the update and and code to move back to the current records, which I see no point at all in doing when you can save the record with one line of code.

If you changed th ecode of th enavigation buttosn to come back to the current record then how are you going to move to another record?

Use the navigation buttons fro waht they are there for and another save button for saving the current record.

.. buttons as såg suggests ... Sorry, spg :o)

OK, jeg kommer nok til at lave egne navigationsknapper.
Jeg vil gerne give nogen af point til spg men er ikke på listen. spg skal nok give et svar og ikke kommentar

You can use the button wizard for making your own but you need to add further code to take into account errors if you try moving past first and last records.

Ja, det ved jeg. Det var også derfor jeg helst ville bruge access egne knapper. Den viser jo også postnummer/antal poster. Men jeg må jo lave det manuelt.

Cant you just add a SAVE button and still use Access's own buttons?
Making you rown isnt going to give you anything extra.

For example the if you have your own "Next Record" button isnt it still supposed to move to the "Next Record" just like Access own?

Jo selvfølglig skal den gå til næste post når man trykker næste post. MEN mit problem er at når man har ændret noget i posten og man svarer ja til at ændringen skal gemmes (efter at have klikket nextrecord) så gemmer den selvfølgelig og går straks til næste post. Nu står man så og kigger på den næste post og kan godt være i tvivl om hvad det var den gemte. Derfor vil jeg gerne have at den bliver ved den post som man har ændret i, efter der er blevet gemt.

Måske kan det løses ved oprette en savebutton som er inaktiv indtil dirty=true.
Når dirty=true så skal nav.knapper gøres inaktive og savebutton aktiv. Efter klik på save spørges om der virkelig skal gemmes ellers fortryd.
Findes der en event når en post bliver dirty=true?

"... Nu står man så og kigger på den næste post og kan godt være i tvivl om hvad det var den gemte ..."

So what you are saying is when you press "Next Record" you DONT infact want to go to the next record. So what is th point in pressing "Next Record" if all you want to do is SAVE?

There is an event OnDirty but you cant test using

If Me.Dirty ...


to see if data has changed.

If you want to disable a save button you will need to have code in a number of events to change the status of the save button. a similar method is to just let the button be enabled and just exit the sub if the data hasnt changed


If Not Me.Dirty Then Exit Sub

You could also have code in the BEFORE UPDATE event which asks the user if they really do want to UPDATE and move to another record.

Ok nu er der vist nok muligheder at arbejde med. Tak for det.

thanks, drop a comment if you need futher assistance here.