Question

I am using the MS Access Sharepoint Migration Wizard to move a database(tables) to Sharepoint lists. Generally, this works well but:

I do have a table "tblProducts" (PK "PID" autonumber long) and a table "tblProductsSpecs" (PK "PID" no autonumber long) which are connected via PID in a one-to-one relationship. I.e. table tblProductSpecs does not have an autonumber and the PK is the same as in the main table, tblProducts.

This setup works as it should in Access as tblProductSpecs just stores additional information about the product.

But when the Sharepoint Wizard moves the table tblProductSpecs to a list, it "autonumbers" the PK field PID and therefore destroys the link between the two tables (as Sharepoint's autonumbers for PID in tblProducts and PID in tblProductsSpecs now differ)

I added a autonumber PK to tblProductSpecs in order to give Sharepoint "something to mess with" but Sharepoint does not seem to recognize the relationship between the two product tables and does not update the PID in the tblProductsSpecs to the new PIDs from tblProducts which Sharepoint automatically generated.

Does anybody have a idea on how to make this work? IMHO this is a bug. Other, more complex m:n / 1:n relationships work just fine. Just the simple 1:1 relationship seems to break Sharepoint LOL.

Any input would be highly appreciated!!

Best wishes, Martin

No correct solution

Licensed under: CC-BY-SA with attribution
Not affiliated with sharepoint.stackexchange
scroll top