Jump to content
Software FX Community

Tip for 5.5 -> 6.2 migration (CHART_HIDDEN constant is different)


User (Legacy)

Recommended Posts

Hi All,

We generate SQL outside of ASP for our charts. I was puzzled when modifying

our ASP to work with 6.2 in addition to 5.5, because the y-axis would go to

10000000000 (lots of zeros) or the w3wp process would go to 100% utilization

until I killed it.

After puzzling over this a bit, I discovered that the CHART_HIDDEN constant

is different for ChartFX Internet 5.5 and 6.2. Normally this would not be an

issue, because the appropriate ChartFX include file would handle it.

However, in our case where we use non-ASP code to generate the SQL, we had

duplicated the CHART_HIDDEN constant in our non-ASP code, and so we needed

to write a special routine to lookup the chart engine from a system table

and then use the appropriate CHART_HIDDEN value in the resulting SQL.

This is obscure, but wanted to document it in case anyone hit the same

stumbling block.

Regards,

-Frank.

Link to comment
Share on other sites

Hi All,

We generate SQL outside of ASP for our charts. I was puzzled when modifying

our ASP to work with 6.2 in addition to 5.5, because the y-axis would go to

10000000000 (lots of zeros) or the w3wp process would go to 100% utilization

until I killed it.

After puzzling over this a bit, I discovered that the CHART_HIDDEN constant

is different for ChartFX Internet 5.5 and 6.2. Normally this would not be an

issue, because the appropriate ChartFX include file would handle it.

However, in our case where we use non-ASP code to generate the SQL, we had

duplicated the CHART_HIDDEN constant in our non-ASP code, and so we needed

to write a special routine to lookup the chart engine from a system table

and then use the appropriate CHART_HIDDEN value in the resulting SQL.

This is obscure, but wanted to document it in case anyone hit the same

stumbling block.

Regards,

-Frank.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...