Multi-Table Query does not allow any fields to be edited

[NJMike64]

Hi all,



I have a query that combines 2 tables on it with a linked Master-Child field between them, however, when I run the query (or the form that I created the query from), none of the fields are editable.

any clues on how to resolve this?

Thanks
mike

[CJ_London]

master data should be on main form, child data in a subform - basic rule is one table per form

[RuralGuy]

Maybe this link can help: http://allenbrowne.com/ser-61.html

[NJMike64]

@AJAX - Yes I agree, but this is a special case.

@RURALGUY - Thanks. I think I know the problem.

In my test db, all the tables and forms are within access and it works fine. However, in my deploy db, I have moved all the tables to sharepoint and it seems sharepoint does not maintain indexing the same way nor does it maintain the relationship between tables the same way. Does that make sense?

Mike

[RuralGuy]

It does to me. I've heard that before.

[NJMike64]

Ok, well that really sucks. Now I have to really think out of the box, and maybe someone has a thought. Basically I have 2 tables, one called room inventory, that, you guessed it, has the complete inventory of equipment in a room. Unique values are the Room Id and a field called uniqueSN that is combo of the part serial number and the part model number (this is because some serial numbers are duplicated in different vendors).

I have a second table called changelog. This is for the team that handles the inventory adjustments to enter in what changes they have, such as Asset Tag, add a new part, remove a part, move the part to a different room.

I was hoping to be able to join the 2 so that I can have a list of changes and just click on a button to copy the change information to the room inventory, if that makes sense.

Thanks
Mike

[RuralGuy]

If I think of something I'll post back but don't hold your breath.

[CJ_London]

you can try changing the form recordsettype to dynaset (inconsistent updates) however this will almost certainly require additional code around populating FK's and potentially updating 2 tables - just because you don't intend to doesn't mean access knows this. But may not be relevant to sharepoint