Hi all, I am very familiar with ver

[johnny9864]

Hi all, I am very familiar with versions 5.x, I was wondering if in present versions 6.0 and up Sage made at least an effort to correct the big obvious problems:

[ul]
[li]Being a local administrator to run ACCPAC[/li]
[li]Using ODBC as the only connection for reporting[/li]
[li]Using Crystal Reports as the only reporting possibility[/li]
[li]Showing by default oldest documents at top in finders[/li]
[/ul]
And I am certainly forgetting some that are less annoying.


I am pretty sure that they didn't do anything but someone can ask and hope...

 

[ettienne]

Yes
No - you can however easily switch to the ODBC reports in most cases for invoices, PO etc. Mostly this is a non issue.
Yes - it's been that way in 5.x
No

Sage 300 Certified Consultant

 

[DjangMan]

Well - for #3 there are some more options such as Sage Intelligence and SEI. But for printing invoices, transaction listings, etc from within the Sage desktop - it's Crystal.

 

[ettienne]

Maybe I misread #3: using CR as the only option. Nothing stops you from using other reporters, I use SSRS for reports and it works well. You can also use BI tools like Qlikview etc, it's all up to you and your skills.
Yes native reports are still CR and there is nothing wrong with that.

Sage 300 Certified Consultant

 

[johnny9864]

Maybe there is nothing wrong with using CR as the report engine but the real problem is using ODBC as the connection method for the reports. I have a customer using item descriptions that take about half a page in that case the ODBC connection cuts the text. At least if I had the possibility of printing from somewhere else it would make their life easier.

 

[ettienne]

It's not the ODBC connection that is cutting the text. If you believe that then you have a fundamental misunderstanding of Crystal Reports.

Sage 300 Certified Consultant