Feedback

[Trouble12]

I would really like to see a course for modifications of some of the reports. I have modified some of the reports and it is possible but it would help if there was some kind of guidance. Also I have not found an Advanced Crystal Reports class that uses MAS 500 ERP they all seem to be centered around Timberline.

[Ralph]

I'll second that.   A Crystal class that is focused on the use of Crystal with MAS500 is a good idea.   There are plenty of Crystal classes out there, but a class geared specifically on using it with MAS500 would be great.

[dleewms]

I am a Certified Crystal Reports Trainer and Reports Writer.  For the last two years, I've been contracting at a company using MAS500.  Would be very interested in knowing what information others would like covered in an Advanced Crystal Reports for MAS class.

Thanks!

[dhale]

Does anyone know why the default Crystal Reports still have catalog references in the tables like Feb03_app rather than the MAS500_app.  Also, some of the references point to Acuity_app.  I know there's a knowledgebase article on when you customize Crystal you need to update the datasource, but maybe getting rid of of these catalog references and old Acuity_app would help everyone out?

[DGill]

I would assume those are test databases that the MAS500 developers were connected to when creating/modifying these reports and consequently got saved as part of the report definition.  If they were to reset the database location to MAS500_app prior to deploying the report, then this nuisance would go away.  The ones pointing to Acuity_app are probably old reports that have not been modified in a while.  I believe Acuity_app was the default name of the deployed database several versions ago.

[SHulme]

A utility was made available about 6 months ago to standardize database name references across all Crystal reports. It was determined that this could substantially reduce unnecessary overhead and improve performance by eliminating the need to run several stored procedures designed to ensure compatibility of the report with the underlying database object references. The hot-fix containing this utility is provided on request by Customer Support.

Going forward, all reports delivered with updates and new versions of MAS 500 will use the standard database naming convention of mas500_app.