Sage 100

Thoughts please on enabling the CS ODBC Driver for MAS200 4.50 SQL...is this a viable solution for slow report printing for the SQL version of MAS200 or only ProvideX you think?

SQL is slow in reporting? I thought this was THE reason for going with the SQL version. Are your tables optimized?

The ODBC for the SQL version does not use the ProvideX ODBC, so the CS version of that ODBC would not apply.

:) You would think it would be different with SQL. It's really just GL reports, but we're in the middle of an action list of either trying this or testing a server move.

Well, I guess Phil answered my question. That's exactly what I was wondering...since the Sage document does not specifically list it being an option for the SQL flavor.

Are these Standard reports on the menu or are they custom crystal reports? I would write a custom report similar to what you are requesting against the SQL database. I think the issue is more in the processing work files not the actual part where crystal reports screen opens up. If that is the case with the processing work files - I would log a case with Sage - there are definite bottle necks in various areas and they just need to tweak the code to speed it up.

Jeff - I forgot to answer your question. IT has worked to optimize the whole set of MAS_XXX tables. Johnny - thanks for your input. They are the standard GL financials...I think i will be calling Sage shortly. Thanks everyone for your responses.