Cannot run make-table query

[Anthony Bollinger]

When I run a make-table query in my Access 2003 database, I receive error:

Record(s) cannot be read; no read permission on 'Measures'.

Please note that I can open table Measures (linked) and edit, add, or delete
data in table view, so I believe the message is misguided.

While this may possibly be security related, it should not be. We had put
this database through the security wizard, but when deployment did not work
out, I did the following three things:
1. Gave Admin full rights on all objects.
2. Added Admin to the Admins group, which has full rights.
3. Gave the Users group full rights to all objects.

I have rechecked these settings and all checkboxes (except ones grayed out)
are checked for all of these situations.

Any ideas?

Thanks!
Tony

 

[KARL DEWEY]

Post the SQL of your query.

 

[Pat Hartman]

A warning for you and any one else who tries to implement security. MAKE a
BACKUP or two or three and put them in safe places. If you mess up
security, you can lose access to your database for good.

My suggestion is to go back to that backup copy.

 

[Anthony Bollinger]

Here it is, hope it helps:

SELECT DISTINCTROW Inventory.[ItemNumber], Inventory.[Sequence],
Inventory.Year, Inventory.Code, Inventory.Description,
Inventory.[AdvertisedPrice], Inventory.[ExtendedDescription],
Inventory.Notes, Inventory.MeasureKey, Inventory.Photo, Inventory.Service,
Measures.MeasureText INTO WebExport
FROM Measures RIGHT JOIN Inventory ON Measures.MeasureKey =
Inventory.MeasureKey
WHERE ((Inventory.[AdvertisedPrice])<>0)
ORDER BY Inventory.[Sequence]
WITH OWNERACCESS OPTION;

And I have some more information. The original error message I reported
references a table in the query (Measures) but if I remove the WITH
OWNERACCESS OPTION, then I get this error message:

Could not create; no modify design permission for table or query
'WebExport'.

Which is the table I am trying to create. I have triple-verified that both
the Admin and the Users group have full (administer) permissions to all
objects, including the database and new tables.

KARL or anyone run into this type of thing?

Thanks!
Tony