May 10, 201114 yr Hi, If I add an SQL view to the relationship graph in FM a pop-up comes up with: The table "xyz" does not provide a pre-defined unique key... If however I chose the underlying table instead of the view then filemaker properly identifies the primary key and the pop-up is not shown. The SQL table of course has the PK. Question: is there a way to construct the view so FM will recognize the PK of the underlying table? Perhaps indexed views should be used? If I simply choose the field for the unique-key in FM then I'm afraid filemaker will create its own indexes, performance will suffer and I've read somewhere that there might be issues with refresh, etc.. Did anyone get around this problem? Thanks!
Create an account or sign in to comment