(Posted to CFusion & Java yesterday)
We recently upgraded our version of CFusion to 6 (from 5). We had developed an
intranet knowledge sharing application using CFusion 5 and thought that this
would work without adjustment on CFusion 6. Among other smaller problems, we
found a big problem in the explorer-style navigation tree which uses CFTREE to
call information from a MS Access database. This had worked well in CFusion 5
but after the upgrade, items were posted twice to the tree (despite only being
in the database once) and subtopics were being posted in the main category
nodes - a proper mess.
As no line of code was changed whatsoever (neither in the CFTREE code nor the
database), the presumption is that there is some issue with CFTREE and CFusion
6. Is anyone aware of what might be happening here - is there some known issue
or bug in CFusion 6?
CF
ciaranfarrell - 30 Nov 2004 08:12 GMT
The problem was with the call to the database. There is a big difference
between CF 4.5 and CF 6.0. We created a query and had CF loop through the query
until CFTREE was populated by all entries in the database. Each entry in the
Access database had a unique ID and a name (Topic -> Subtopic -> Description
whereby the description had a unique ID). We created the code in CF 4.5 to
select and group using the Topic ID, SubTopic ID and unique ID only (ie numbers
only). This worked. However, when we migrated to CF 6.0 everything got messed
up (see above). We solved this by calling not only #ID# (unique ID) but ID#ID#.
This combination of name and ID was accepted by Access. I haven't a clue what
changed in CF 6, but this is the workaround