Field won't allow edits?

M

Maury Markowitz

I have a form bound to a query (view) in an MDB (Access 2003). Most of the
fields on the form are "Locked = true", but there is one I would like to
allow edits on. I have set the form as a whole to "allow edits", and set that
field to locked=false. The cursor will enter the field but not allow me to
change the value.

The view includes the pkey from the underlying table (and it is shown), as
well as a limit in the WHERE that joins on another table. The basic purpose
is "get these columns from this table where there is no matching record in
that table).

It seems it should be OK, what am I missing?
 
M

Maury Markowitz

Joseph Meehan said:
I can't quite figure out what you are doing with those tables, etc. but
I am going to guess that if you take a look at the relationships you will
find that entering data into that field is not possible since that filed
does not have a direct reference to a single field in a single table.
Click to expand...

I'm pretty sure this is the case too, but I can't find the problem.

Table 1 is a list of stocks. Included in the table is the information about
the next dividend that will be paid.

Table 2 is a list of dividends that have been paid.

The application copies the information from Table 1 (which has many other
fields as well) into Table 2. That way the form can figure out which ones
have been booked, and which ones have not. Additionally we can report on
historical dividends by looking at Table 2.

The form in question is bound to a view on Table 1. The field in question is
bound directly to a field in the table. I'm sure it's something obvious, but
I don't see the problem.
 
R

Rick Brandt

Maury Markowitz said:
I'm pretty sure this is the case too, but I can't find the problem.

Table 1 is a list of stocks. Included in the table is the information about
the next dividend that will be paid.

Table 2 is a list of dividends that have been paid.

The application copies the information from Table 1 (which has many other
fields as well) into Table 2. That way the form can figure out which ones
have been booked, and which ones have not. Additionally we can report on
historical dividends by looking at Table 2.

The form in question is bound to a view on Table 1. The field in question is
bound directly to a field in the table. I'm sure it's something obvious, but
I don't see the problem.
Click to expand...

It is very easy for a multi-table view or query to become non-updateable.
Before you wonder about why your FORM won't let you edit you should test to
see if you can make edits directly in the view. If you can't then you have
to fix that (or change how you're doing things).
 
M

Maury Markowitz

Joseph Meehan said:
Are you working with queries? If so start with the last one in the
chain before the form. Can you make the changes there? If not go to the
next level query until you find where the problem is.
Click to expand...

This was excellent advice. I found that any SUM makes the recordset
unupdatable.

So I removed it. Now the query is indeed editable (if you open the query,
you can type in data).

However the form still won't allow edits!

Maury
 
Top