Crystal and Providex Database

[ppark001]

I am using Crystal 8.0 with the Accounting Software, MAS200. This version of MAS200 uses Providex for its database.

My question has to do with Crystal's performance with this database. In my reading in Tek-Tips, most experts advise using views, stored procedures, etc for purposes of performance. However, Providex is not like Oracle or SQL 7 where you have a database administrator to create stored procedures. It is a closed database and does not utilize indexes.

It seems that no matter what I do, Crystal always goes through the database sequentially. The only thing I know to do to help performance is to (1) use SQL statements for queries (2) don't use left joins (3) deselect "dirty read" and "burst mode" in the ODBC setup.

Am I correct on my take on this? Please set me straight if there are other ways to help on performance.

Thanks,

Paula P.Park, A.C.E.
Authorized Crystal Engineer

 

[reporting]

I've never heard of the Providex database...

The most important thing to look out for if you want to increase Crystal performance is to use indexes: you should ALWAYS do your Record Selection & Grouping on indexed fields. Additionally, under certain circumstances (hidden detail lines / 'Perform Grouping on Server' switched on / use of certain SQL aggregate functions), you can increase performance even further.

HTH,
John Marrett
Crystal Reports & Crystal Enterprise Trainer

http://www.e-reporting.ca