subform fails with linked tables

[byterbit]

Have a standard working form/subform that fails when I split the tables


I tried recreating the subform with the tables already split off into a "backend" mdb; the subform still fails to populate.

Master /child relationship is simple, just based on one foreign field (id in master table, exam_id in child)

This is the sort of simple subform stuff I've been doing for years; but I never tried it with linked tables. Can it be done ?

[RuralGuy]

Abrolutely! Are your relationships still intact after the split?

[byterbit]

Relationships unchanged. Nothing very formal here; just created the subform with the wizard , and it worked fine.
I tried to formalize matters to fix it ( used the relationship window ; made no difference) and then based the subform on a query that linked the two tables; that had an interesting effect in that no editing could take place in the subform. I could change data in the table, and it would show, properly, on the form, but no adding/editing on the form. Properties showed nothing locked.

[RuralGuy]

It sounds like you had created a non-updateable query. http://allenbrowne.com/ser-61.html

[byterbit]

Yes, the query did not allow updates as one side, though indexed, was not set to unique; setting it so seems to have been all that's necessary. Thanks for that !
Next step will be rebuilding app to use the query.

On the broader issue, I'm still confused though . Once I brought back the tables into one MDB everything was happy (without adding the above query as the basis for the subform); it seems the linking logic for the form/subform works fine if the tables are in the main mdb and bombs when they are split.

I dont think running the formal Access "spliter" would make any difference, but I'm too tired at the moment to test it.