Deletions vs. Edits

[jparker1954]

Just when I think I'm getting it. I've got a form that I want to allow people to add or delete records, but NOT edit records. I thought that changing the Form properties to Allow Deletions and Allow Additions, but NOT Edits would do this. Silly me.

Is there a way to Allow Deletions without allowing Edits. I need to have some control over what's going in and out of the database.

[jparker1954]

What I'm really trying to do is control changes to a database that I'm updating a by using union queries and append queries to add new information daily.

I'm concerned that if people delete or edit a record in one of three databases I've used in the union query, that change won't show up in the final appended database. The appended database will still show the old information. Is there a way to prevent that, short not allowing edits or deletes and having the people contact me directly to manually edit or delete entries?

[June7]

Did you also set Allow Edits property to No?

[jparker1954]

Yes. Doing that made the Delete Button useless. Allow Deletions- Yes, Allow Additions-Yes and Allow Edits-No. Delete Button won't work. Change Allow Edits to Yes, Delete Button works.

[June7]

Interesting, I tested that setup and it does exactly what you are looking for. I could add and delete records but not edit fields.

Do you want to make the db available for analysis?

Can't say if there is a better way, don't know your data and business situation. My first question is why appending and not linking to data?

[jparker1954]

Are you using Access 2010? The file format that I'm using is Access 2000, unfortunately.

I think the problem is the code that is used for the Delete Button. I think the acEditMenu might be causing a problem, but I don't know what to use otherwise. Code is:

Private Sub DeleteRecord_Click()
On Error GoTo Err_DeleteRecord_Click

DoCmd.DoMenuItem acFormBar, acEditMenu, 8, , acMenuVer70
DoCmd.DoMenuItem acFormBar, acEditMenu, 6, , acMenuVer70
Exit_DeleteRecord_Click:
Exit Sub
Err_DeleteRecord_Click:
MsgBox Err.Description
Resume Exit_DeleteRecord_Click

[jparker1954]

I was correct about the code. I found a thread in another forum that shows the code for the Delete Button in the 2007 version. This one works perfectly in my 2000 version and does exactly what I need it to do.

By the way, I'm using union queries and appending data, because I have 3 remote locations that enter harvest data into local databases, then I combine that data into one database that we can track.

Thanks,

[jparker1954]

In case anyone else needs it, the code that works is:

Private Sub CmdDelete_Click()
On Error GoTo Err_CmdDelete_Click


DoCmd.RunCommand acCmdSelectRecord
DoCmd.RunCommand acCmdDeleteRecord
Me.Refresh

Exit_CmdDelete_Click:
Exit Sub

Err_CmdDelete_Click:
MsgBox Err.Description
Resume Exit_CmdDelete_Click

End Sub