auto save problem

[rashidzaib]

hy bro and sis
i hope all r fine
i have one problem in access and that is when i am entering the new data it is save automatically. i want to save data when i press save button otherwise it will not save data and also for update i also want updation through command button is there any solutiion for this.
any help should realy be appriciated.
thank u
ur truly
rashid zaib

 

[missinglinq]

This will cover both situations. You don't really need a command button to save the record. If a new record is entered, it will ask if the new record should be saved when you try to go to another record or close the form. If an existing record is updated, it will ask if the changes should be saved when you try to go to another record or close the form.

Private Sub Form_BeforeUpdate(Cancel As Integer)
If Not (Me.NewRecord) Then
 If MsgBox("Would You Like To Save The Changes To This Record?", vbQuestion + vbYesNo + vbDefaultButton1, "Save Changes to Record ???") = vbNo Then
  Me.Undo
 End If
Else
 If MsgBox("Would You Like To Save This Record?", vbQuestion + vbYesNo + vbDefaultButton1, "Save This Record ???") = vbNo Then
  Me.Undo
 End If
End If
End Sub

Linq

 

[adnanahmed]

For auto save problem

i think u can solve this problem if remove the recordsource of the form and also making the fields unbound.
And then on Save command button open a recordset to the table and save the record.
but have to write some code.
may this help u
bye.

 

[Pat Hartman]

If you're going to go to the trouble to use unbound forms (and it is more trouble than you can imagine), you should probably be working in some other development environment than Access. The primary reason to use Access is to take advantage of the things that Access does for "free". Things you don't need to code. In fact, although all professional Access applications require some code, that should be your last option, not your first. Learn how the events work and you can control bound forms with almost as much precision as unbound forms with 1% of the code.

 

[missinglinq]

You're exactly right, Pat! Why in the world would anyone want to get involved in the gigantic hairball that unbound forms are, rather than simply copying and pasting a dozen lines of code, simply to be able to check to see if the user wants to save a record/change or dump it?

Linq

 

[adnanahmed]

i only suggest the way...
So, why u people r so anguish

 

[rashidzaib]

auto save problem solved

hy bro
sorry yesterday i did not used internet. and thank u very much for help me and giving me very nice information .
this code i have tried and working very nicely
thank u very much

 

[Rabbie]

i only suggest the way...
So, why u people r so anguish

I think they were just trying to say that your way had unnecessary complications and there was a simpler way of doing things. The best solution is the simplest one that meets all requirements.

 

[missinglinq]

Glad it works for you, rashidzaib!

Ahmed: no one was angry, but you simply don't need a Cruise Missile to kill a fly! Changing a bound form to an unbound form would mean a huge amount of work! Why do that when 12 lines of code will accomplish the task and not require a complete rework of the form?

Linq ;0)>