I am about to upgrade to 8.0. Are there any problems I should be aware of that any of you have seen after the upgrade?

don't know as we are still at 7.3
I had one person ask about my plan spec report yesterday. they said it worked fine at 7 but quit at 8.0. (Yes, people actually use some of the reports I have made available!)
Obviously at this point in the game I have no clue if there is a problem with custom reports or if something needs to be reset.

No problems with 8.0 so far, the main thing is custom reports need to be verified.

Some random thoughts regards reports & the spec report previously mentioned - which I find working at v 8.0 - a few changes were made and then it was fine.

v8
substantive changes in 415 Report
(which our 415 custom report was based on)
substantive changes in the structure and content
of tables underlying some specs dealing w/ limits. There
were some changes here, and subreports are
used I think in the header, as well as lookup fields (codes) for various fields. useralpha1, 11, 12 were moved... somewhere on the frontend, the new table listed in what's new.

Not sure what effect the subreport structure will have on existing
specs reports; limits and etc appear to be what is on the subreport. If you look for a subreport it won't be found on disk, as it's embedded in the particular crystal report spec (1-8 report).

On how to integrate a spec report with say, a contribution report, or 415 report - I'm guessing that the limit table is linked by plan year. Tom's report as an example was not a spec report that shows lim/tax yr limitations, nor was it linked to contribs, so the assumption would be that the report is okay, with some minor alterations.

I'm not 100% sure about the assumption that the only change in spec reports was around limits, and limitation year appears to be an important link. I have yet to find a top heavy flag.

Having said that, in tom's spec report, the following fields
are not recognized;
{PLANSTAT.USERALPHA11}+{PLANSTAT.USERALPHA12}

@blank
if {PLANSTAT.USERALPHA1}='' then 'enter comp def in user alpha 1 in specs'

The alpha fields were moved to a different table and I'm not sure yet which front-end report table utilizes these... taking the easy out, quickly replaced with Parameter field ?strAsk:
Prompting Text: Enter Comp Def etc etc
type: String

So the report ran fine having replaced the fields that were moved. The percent limit field in admin isn't behaving like we thought it would, but other than that, 8.0 works fine so far.

Regards,

Bill

thanks for the update.

as usual, looks like some extra work when switching to 8.0 in regards to the Crystal reports.