Position Changes to SYN (OpenInsight 32-Bit)
At 12 AUG 2006 12:08:38PM Charles DiCarlo wrote:
I am currently implementing Freedombase and due to the way the data is retrieved, they recommend that you do not include an underscore separator. I am rename my columns and as I do, the position is changing from the number (eg. 1, 2, 3) to SYN (eg. SYN 1, SYN 2, SYN 3). If I save the table and bring it back, the SYN's are still there. If I change the Position to a different value (eg. 101, 102, 103) and save the table, it works. I then have to go back and rename the Position to what I want it to be (eg. 1, 2, 3).
1. Why is this occuring?
2. Is there a way to prevent it?
3. Is there a better way to restore the Position?
Thanks for any help you can provide.
cdc
At 12 AUG 2006 08:34PM Steve Epstein wrote:
I have had this problem with the table builder and dictionary building for years. There seems to be no problems, however, even though the attribute difintions are marked as synonyms (SYN).
At 13 AUG 2006 12:43AM Warren Auyong wrote:
You're experiencing the joys of DICT.MFS
The first "F" type record for a FMC is marked with the master flag and any other "F" types to the same FMC are "SYN"onyms.
There are many kludgey solutions to get around this. I normally edit the dictionary records, delete the ones I don't want, then copy and delete them to a temporary datafile (non-dictionary), clear the masterflags, delete the %FIELDS% record in the dictionary and then copy back to the dictionary first the ones I want to be "masters" then the rest.
At 13 AUG 2006 05:53AM [email protected] wrote:
In the grand scheme of things, it's not that big a deal if your fields are flagged as synonyms. It's only the keys that really need to be defined as a master for some indexing things.
The Sprezzatura Group Web Site
World Leaders in all things RevSoft
At 13 AUG 2006 01:08PM Richard Hunt wrote:
So then… simply checking that the item being worked on (or edited) is the actual same item that is the master, would fix the flaw.
Some bugs are so easy to fix.
At 13 AUG 2006 06:13PM Warren Auyong wrote:
In theory all you need to do is delete the "master" and the next time you edit an "F" type for that FMC it should become the master. It doesn't always work that way, the culprit being the %FIELDS% record.