It really depends on how the data will be presented and bound in Excel and how much concurrent editing/deleting of the same record you're likely to have. The safest option (and simplist) is pessimistic locking, this means that the database takes care of concurrent editing of rows, this may or may not be a good option depending on how much concurrency the application is likely to have, but ensures that once a user starts editing a row, another user cannot - it's most useful where a user maintains a single session.
Optimistic locking is typically used where you disconnect your data, think read the data into your form then close the connection, then at some point later update a record.
Either way you need to be careful, optimistic locking puts the emphasis on your application to prevent accidental overwriting of data when concurrent editing occurs, but pessimistic locking requires steps to reduce the likelihood of deadlocks.
As to the cursor, again it depends on your implementation. If you favour an optimistic approach, you can go for a forward only cursor which is very fast, however if additions and deletions are likely and you need to preserve data integrity then a dynamic cursor is preferable as it updates when other users make changes.
So it's not really a straightforward question, it really depends on how you are implementing the database in excel.