all fields in editable subform behave as locked even though they a

[Guest]

I'm trying to develop a small database to manage vacation requests, using MS
Access 2003 SP3.

I created a subform for detail of vacation requests by the selected employee
which fall within the specified time period. The user should be able to edit
or delete existing requests (most fields, but obviously not the approval
flag, and not the record creation date). New records will be added on a
different form.

If I open my review/edit subform directly, in datasheet view, I can edit the
fields that I want users to be able to edit, and reset any approval flag,
update the record changed date/time, etc. All works perfectly, life is good.

I created a main form showing personal information (and some extra buttons
made visible only when the selected user is a manager), which has a subform
control referencing the above subform object. The main and subform objects
are not linked with Child/master, because of multiple unrelated selection
criteria.

When I open the main form with the exact same subform, using the exact same
updateable record source, still in datasheet view, the subform fields all
behave as though they are locked. In design view, the properties lists show
that the subform fields that I need to be able to edit are clearly not
locked. I can still delete records within the subform control; I just can’t
edit.

Suspecting corruption, I created a new database and copied the relevant
objects over. My problem is still there.

I am told by a respondent on another forum that my database works just fine
for him, and that I should suspect Access 2003 SP3 as the reason for my
distress. I can’t find anything anywhere about SP3 that supports this
theory, nor have I found another post with a really similar problem.

 

[Guest]

I can't remeber exactly, but I have read that this can happen with SP3 with a
control that has format (format property of the control), but I can't remeber
exactly the problem or where I read it.
You might try searching the groups with "SP3"

 

[Guest]

Well, thank you, but I did this already. As stated in my original post: "I
can’t find anything anywhere about SP3 that supports this theory, nor have I
found another post with a really similar problem. " Perhaps you could
search again and find more relevant results?

I will take the database home again, and see which SP is current at home.
If it's SP3 both places, I'll try reverting to an earlier version at work,
though that is a lot of effort, and doesn't resolve the fact that many of the
intended end users will probably have SP3. Alternative ideas anyone?
Circumvention? Workaround?

 

[Guest]

I took this beast home last night. I'm using Access 2003 SP2 at home, so now
I know first-hand that it isn't SP3 that is causing the problem.

I also created new forms, and based them off similar data, using SP2. I
think my new subform worked properly until I added a filter to the main form.
I need to repeat the experiment and write down each step as I take it, to be
sure. But once the subform began to misbehave, locking all the fields instead
of only the ones I specified, then nothing that I had time to try last night
would restore the proper behavior. I did not have time to try removing the
filter for the main form to see if that would restore proper operation.

I do think there is a learning opportunity here, and what ever we learn is
probably worth sharing.