Is it duplicating the actual table, or just the Table Occurrence on the graph?
The former is unusal and a bug, the latter is expected behavior. A table occurrence is only a link or reference to the original table...kind of like a DBA in the business world. Multiple TOs can access the data of a single table, but they all access the same data. I suppose it in a small sense like looking into a room through different windows.
Duplicating the table -- that is, it creates another "shadow" table in the FMP file.
Tomorrow I'm converting a Windows 2003 Server box from FMS 11 to FMS 12 and will be installing the files onto it, will be interesting to see if the behaviour changes.
So on the Relationship Graph?
That is expected behavior, then. Those are not the actual tables. They are Table Occurrences. You can not have the same Table Occurrence of a table connected twice to another table occurrence. In the case that you try to, it creates another Table Occurrence to accommodate the new "view" into that table.
Read both of Vaughan's posts again carefully, especially the first line of his reply. Vaughan has been using FileMaker long enough to know the difference (and is, IIRC, Certified on either FMP 10 or FMP 11).
The "shadow tables" are the entries FileMaker makes in the in the list of TABLES, not just another TABLE OCCURRANCE on the Relationship Graph. The first TABLE entry has the calculation fields he has added to supplement the data fields from the ESS table. The new (unexpected) TABLE entries do not.
So what he is describing is UNexpected behaviour.
Any advice on this unexpected behaviour?
I have a feeling it's something with the Actual ODBC driver running on the Mac OS X server. Will let you know how the file behaves on the Windows 2003 Server box I convert from FMS 11 to FMS 12 today.
Appreciate the input rob. That was why I asked the question the way I did. I wasn't sure where Vaughan's level of expertise was from reading the email. Now that I'm on the forums I can see he is certified in 9, 10, and 11.
And I agree with Vaughan...definitely sounds like a driver issue. I know the guys from Actual pop in on the forums on a regular...maybe they can lend some more insight. I had this problem once, but I was doing a whole lot of stress testing on the server and flipping a lot of settings and such. So I assumed I had thoroughly corrupted something on the OS or FM Server. So I have nothing helpful to add. lol
Got the new server running, the file is now working as expected and no longer duplicating the tables.
If the Acutal people want to contact me for details etc, send a private message.
I'm certified in FM 8 as well.