Why is my query read-only?

S

Stapes

Hi

I have a query linking my Customers table & my Contacts table, so that
all the information can be displayed together on the screen for
updates and deletions. Unfortunately, the resulting data is read only.
I didn't tell it to be read only. Why has this happened?

Stapes
 
J

Joan Wild

Open your query and switch to SQL View (view menu). Copy the SQL statement and post it here.

Alternatively you can create a form for the Customers, and put subform on it (for the Contacts).
 
F

fhwa

Hello, I'm having the same problem and I cannot figure out the
problem. Here is my SQL and the design view is pulling information
from 5 different tables that are all related and have primary/foreign
keys. I appreciate the help I need to be able to edit the information
with this query along with a form that is made from it.

SELECT tblStrategicGoals2.StrategicGoal,
tblStategicOutcomePlan.NationalPerformanceGoal2007 AS Expr1,
tblStategicOutcomePlan.NationalPerformanceGoal2008,
tblStategicOutcomePlan.DivisionOutcome2007,
tblStategicOutcomePlan.DivisionOutcome2008,
tblMeasuresAndTargets.Measure2006 AS [Measure 2007],
tblMeasuresAndTargets.Measure2007 AS [Measure 2008],
tblMeasuresAndTargets.Target2006 AS [Target 2007],
tblMeasuresAndTargets.Target2007 AS [Target 2008],
tblEmployeeSOPID.SOPID, tblEmployeeSOPID.EmployeeID,
tblStategicOutcomePlan.OutcomeChampion, tblStategicOutcomePlan.Focus,
tblEmployees.LoginName
FROM tblStrategicGoals2 INNER JOIN ((tblStategicOutcomePlan INNER JOIN
(tblEmployees INNER JOIN tblEmployeeSOPID ON tblEmployees.EmployeeID =
tblEmployeeSOPID.EmployeeID) ON tblStategicOutcomePlan.SOPID =
tblEmployeeSOPID.SOPID) INNER JOIN tblMeasuresAndTargets ON
tblStategicOutcomePlan.SOPID = tblMeasuresAndTargets.sopID) ON
tblStrategicGoals2.StrategicGoalID =
tblStategicOutcomePlan.StrategicGoalID
WHERE (((tblEmployeeSOPID.SOPID)>60))
GROUP BY tblStrategicGoals2.StrategicGoal,
tblStategicOutcomePlan.NationalPerformanceGoal2007,
tblStategicOutcomePlan.NationalPerformanceGoal2008,
tblStategicOutcomePlan.DivisionOutcome2007,
tblStategicOutcomePlan.DivisionOutcome2008,
tblMeasuresAndTargets.Measure2006, tblMeasuresAndTargets.Measure2007,
tblMeasuresAndTargets.Target2006, tblMeasuresAndTargets.Target2007,
tblEmployeeSOPID.SOPID, tblEmployeeSOPID.EmployeeID,
tblStategicOutcomePlan.OutcomeChampion, tblStategicOutcomePlan.Focus,
tblEmployees.LoginName
HAVING (((tblEmployees.LoginName)="dbullock"))
ORDER BY tblStrategicGoals2.StrategicGoal,
tblStategicOutcomePlan.NationalPerformanceGoal2007,
tblStategicOutcomePlan.DivisionOutcome2007;
 
B

Bob Quintal

Hello, I'm having the same problem and I cannot figure out the
problem. Here is my SQL and the design view is pulling
information from 5 different tables that are all related and
have primary/foreign keys. I appreciate the help I need to be
able to edit the information with this query along with a form
that is made from it.
The Group by and Having clauses indicate that this is a summary
query, even though you are not summing anything in the select
statement, Summary queries are read-only, always read-only and
will be forever read-only. Turn off the summary mode.
Open the query in design mode and click the icon with the Greek
letter Sigma on it.

There may be other things in the statement that might make the
query read only, but the Group By clause is a definite cause.

Q

SELECT tblStrategicGoals2.StrategicGoal,
tblStategicOutcomePlan.NationalPerformanceGoal2007 AS Expr1,
tblStategicOutcomePlan.NationalPerformanceGoal2008,
tblStategicOutcomePlan.DivisionOutcome2007,
tblStategicOutcomePlan.DivisionOutcome2008,
tblMeasuresAndTargets.Measure2006 AS [Measure 2007],
tblMeasuresAndTargets.Measure2007 AS [Measure 2008],
tblMeasuresAndTargets.Target2006 AS [Target 2007],
tblMeasuresAndTargets.Target2007 AS [Target 2008],
tblEmployeeSOPID.SOPID, tblEmployeeSOPID.EmployeeID,
tblStategicOutcomePlan.OutcomeChampion,
tblStategicOutcomePlan.Focus, tblEmployees.LoginName
FROM tblStrategicGoals2 INNER JOIN ((tblStategicOutcomePlan
INNER JOIN (tblEmployees INNER JOIN tblEmployeeSOPID ON
tblEmployees.EmployeeID = tblEmployeeSOPID.EmployeeID) ON
tblStategicOutcomePlan.SOPID = tblEmployeeSOPID.SOPID) INNER
JOIN tblMeasuresAndTargets ON tblStategicOutcomePlan.SOPID =
tblMeasuresAndTargets.sopID) ON
tblStrategicGoals2.StrategicGoalID =
tblStategicOutcomePlan.StrategicGoalID WHERE
(((tblEmployeeSOPID.SOPID)>60)) GROUP BY
tblStrategicGoals2.StrategicGoal,
tblStategicOutcomePlan.NationalPerformanceGoal2007,
tblStategicOutcomePlan.NationalPerformanceGoal2008,
tblStategicOutcomePlan.DivisionOutcome2007,
tblStategicOutcomePlan.DivisionOutcome2008,
tblMeasuresAndTargets.Measure2006,
tblMeasuresAndTargets.Measure2007,
tblMeasuresAndTargets.Target2006,
tblMeasuresAndTargets.Target2007, tblEmployeeSOPID.SOPID,
tblEmployeeSOPID.EmployeeID,
tblStategicOutcomePlan.OutcomeChampion,
tblStategicOutcomePlan.Focus, tblEmployees.LoginName
HAVING (((tblEmployees.LoginName)="dbullock"))
ORDER BY tblStrategicGoals2.StrategicGoal,
tblStategicOutcomePlan.NationalPerformanceGoal2007,
tblStategicOutcomePlan.DivisionOutcome2007;
 
J

Joan Wild

This is a 'totals query' - you can't edit a query that aggregates information like this.
 
D

Douglas J. Steele

The odds of a 5 table query being updatable are extremely low (if, in fact,
it's even possible)

In general, you'd use a query like that for a report, where of course it
doesn't matter whether or not the query is updatable. For a form, typically
you'd bind the ID field to a combo box that uses the other table as its row
source, and hence remove some of the tables from the query.
 
J

Joan Wild

Douglas J. Steele said:
The odds of a 5 table query being updatable are extremely low (if, in fact,
it's even possible)

In general, you'd use a query like that for a report, where of course it
doesn't matter whether or not the query is updatable.

Although it was for a report, I had a 7 table query that was updatable, so it is possible.
 
F

fhwa

Although it was for a report, I had a 7 tablequerythat was updatable, so it is possible.

Thanks everyone for your help but after a couple hours of messing with
it at work I just decided to forget about making it work with the way
they had things setup and just merged different tables so their were
only 2 one to many relationships and now it works just fine. Thanks
for all your help though!
 
Top