Hi John,
Unfortunately you can't really change form behaviors with CSS alone so you won't be able to make the popover prevent editing while allowing drag and drop. (We hope to introduce more fine-grained control of editing rights).
You could, however, switch to a FileMaker layout for your popover: that would give you complete control of the editing surface (and let you easily pull the delete button you asked about) while retaining drag ability in the calendar itself. That would also let you use a sub-list of statuses when editing the event, something you can't do in DayBack's popover.
More on using your own layouts for popovers here:
http://www.seedcode.com/pmwiki/index.ph ... entLayoutsFor some more background, when it comes to editing rights, DayBack respects FileMaker's access privileges for the logged in user. But remember that some access rights may not be reflected in DayBack's interface. For example, if you have record level access privileges set so that a given privilege set can't see a record, then that record won't show up in DayBack. No problem.
But if FileMaker's record level access says that a given privilege set can only edit a record under certain circumstances, that record will ''appear'' editable to logged in users since DayBack can't evaluate the access rights until the user tries to edit it. So users will be able to, for example, drag an event to a new date: the drag just won't take and will be reverted after users see a dialog saying the action isn't permitted.
Hope that helps,
John