As Richard oft repeats in his videos, your end user shouldn't have direct access to your tables and queries. A finished database shouldn't expose the end user to the navigation pane where they can directly access queries.

If you want them to be able to see the raw results of a query without being able to edit, create:

a) a continuous form with the query as it's record source with all of it's fields locked so that they have to click a button to open the form(s) you want them to edit with,

b) create a form with a datasheet sub form where the datasheet is locked and/or has "allow edits", "allow deletions", and "allow additions" set to no,

c) create a split form (basically the same as b, with less control) with the "Split Form Datasheet" option set to "Read Only"

In his video Split Forms video, Richard discusses pros and cons of the last method along with some of the pitfalls that historically existed with allowing users to have direct access to your datasheets (table/query view).

Oh, and I guess you could create a fourth option:

d) Use the query as the source for a report

This would be similar to Richard's Embedded Report video where he creates a "reading mode". And then you could apply techniques similar to Buttons on Reports to be able to open add/edit forms.