<hr>what prevents some well-meaing, but possibly error-prone individual, from going in native mode (directly in Access) and even unintentionally changing/deleting, etc the original data?The solution to this sort of thing is to implement Access User Security, and in general to hide the database container window from your users. You can read a brief User Security Tutorial on our website - it includes links to a number of Knowledge Base articles on the subject - and you might find Jack MacDonald's in-depth User Security paper useful. Finally Mark has pointed you to a pretty comprehensive book on the subject - I don't concur with everything he says, but it's one of the most complete looks at securing an Access database. As to creating reports, we find that very few users are proficient enough in Access to actually create reports. What we do see however, is situations where users do create their own queries - we typically create a separate database for users who want that ability, and restrict their ability to edit data in any way from that database. Finally, I should note that where we use SQL Server back-ends, we also implement the SQL Server security model, which operates at a much different level than the Access model.
I would like to have users create their own reports, but I'm worried that unrestricted access (pardon my pun) through Access could result in dependencies getting messed up, etc.