Problem with DoCmd.RunCommand, acCmdSave
as you've already noticed, you don't need the macro to save the
record. access has an implicit save that occurs when the user moves
from record to record (as long as the user has permission to modify
the data in the table). i'm not sure why the macro is getting tangled
up in form permissions -- those things usually come up during testing,
and since you don't need that line of code, you can just delete it.
On Mon, 8 May 2000 10:23:35 -0500, "Art Norton"
>I have a group that for Tables has all permissions except Administer.
>Forms - they have Open/Run and Read Design
>Macros - Open/Run
>Access 97, SR2
>The problem is when I try to save some changes on a form, I get an error
>(2046) that says save is not available. If I comment out the
>DoCmd.RunCommand acCmdSave it runs fine. If I change to the Admin user (who
>has all priviledges, no problem with the DoCmd.RunCommand line.
>Which priviledge does the DoCmd.RunCommand fall under? I can comment it out
>as when I change records the changes are saved anyway. Would like to know
>in case any other problems occur.