What I have found annoying in Crystal 8 is that when you move a report to a different database source, by selecting the original datasource and a new datasource, it will not do it and gives an error. If you do the same thing in Crystal XII it works fine. There is probably a setting, but thus far I still have to revert to XII to do this because 8 will not.
If anyone knows a way around this, I would be interested in hearing it.
Just my observation...
George Hicks
PCI
If anyone knows a way around this, I would be interested in hearing it.
Just my observation...
George Hicks
PCI
--- In vantage@yahoogroups.com, Waffqle <waffqle@...> wrote:
>
> As long as everything is working, I can't imagine any surprises down the
> road.
>
> We don't rebuild any of our reports unless the data definition has
> substantially changed.
>
> On Sat, Aug 13, 2011 at 12:05 PM, al2trace <allen.larsen@...>wrote:
>
> > **
> >
> >
> > In converting from 9.04 to 9.05, the reports changed from Crystal XI
> > Release 2 to Crystal 2008. We did not convert our modified RPT files to the
> > new version of Crystal and for the most part, that seems to be working. Now
> > that we are live on 9.05, we are editing RPT files with Crystal 2008. When
> > we set the database location to a new XML file, some of the date fields are
> > not mapped and no matching fields appear. If I unclick "Match Type", all the
> > fields appear including the one I need. I select it, click "Map" and move
> > on. My guess is that either Epicor or Crystal have changed the date format
> > somewhat. Is this process going to hurt me later?
> >
> >
> >
>
>
>
> --
> *Waffqle Driggers*
> *High End Dev, System Design, Profit Drinking
> *
> *:: 904.962.2887*
> *:: waffqle@...*
> *:: NO FAXES*
>
> *
>
> *
>
>
> [Non-text portions of this message have been removed]
>