RE: Microsoft FRX 6.7 Error
Just ran into this one as well and my solution was a bit different, but similar, so I thought I would share.
The GL40200 stores Segment Number, Value, Description (if you name them). Somehow the guy that loaded the initial COA messed it up several time and probably SQL deleted. We only have 4 Segments, but there were 10 listed in this table. So I deleted all the rows that had a SGMTNUMB > 4
But also noticed that there were funky values in there. Our COA is 3-5-4-4
But there were segment 1 values with a length of 6 in there as an example. Even though the first delete made it so I could load FRx, I also decided to delete bad values out of the table (check links didn't seem to do this, so I took it upon myself), because FRx kicked that initial error from running this query (to load into the FRx tables).
select a.SGMTNUMB, a.SGMNTID, a.DSCRIPTN from CODB..GL40200 a order by a.SGMTNUMB
(Got this from SQL Profiler when the error happened)
Since it is loading that query above into FRx, I don't want junk going in there. So I made a script to get the bad records out of that table completely. In my case, this worked (set for 3-5-4-4). You could make this dynamic and pull from your setup if you wanted, I hard coded the lengths.
DELETE FROM GL40200
WHERE
(SGMTNUMB = 1 AND LEN(SGMNTID) <> 3)
OR
(SGMTNUMB = 2 AND LEN(SGMNTID) <> 5)
OR
(SGMTNUMB = 3 AND LEN(SGMNTID) <> 4)
OR
(SGMTNUMB = 4 AND LEN(SGMNTID) <> 4)