It depends on your setup, but there are a couple of ways:
1) If you're using ESS, you can use a relationship between the SQL table and the FileMaker table. Anything that doesn't have a match on the FileMaker side is missing.
2) Import from the SQL table to the FileMaker table on matching IDs, update with add missing records.
Performance, size of SQL table, specific setup ... these will all affect the best approach.
Thank you Mike for your response, please forgive me if i am being a little slow but what do you mean update with add missing records?
Thanks again Mike for you time but I have re imported a table and am still not getting a dynamic FileMaker version of it.
richard, IMPORT is not dynamic. It's as if you exported a .csv version from SQL and imported the file into FM. It's a 'snapshot-in-time'.
When you connect to an external SQL source (ESS) with the approved sources, then you have a 'live-connect' and any changes in the FM 'table-that-is-view-into-SQL' will appear in the SQL table.
However what Mike is saying that you are not necessarily using ESS and simply importing from the SQL source (if not one of the approved sources, this is your only option).
If you follow Mike's suggestion to show all records (in the FMP table previously imported) before a new import then in the import dialog, select
"Update matching records in found set"
"Add remaining data as new records"
The symbol matching the ID field in SQL and in FM should have the "<->" to show it is a match.
Then what you import will UPDATE existing records (based on match) AND INSERT new records (with no match on ID, because they are new).
Thank you Beverly and again Mike, I have got it, I thought Mike was suggesting a trick that would give me a permanent live version of the SQL in the FM. I am using ESS and the import is less clumsy than my current solution.