Linking Budget and Actual data

[stoopers]

What is the best way to link Budget and Actual data?

Using Crystal 11
Actual data is coming from Iscala; table/view in Crystal
Budget data is coming from Access DB.
Customer code is common field between the 2 tables.

Budget data may contain new customer codes that will not appear in actual data.

Actual data may contain customer codes that will not have budget data.

Currently have a Left Outer Join from the Actual table to the budget table - but experiencing extremely long run times.

 

[synapsevampire]

Crystal doesn't have tables or views, so try to learn what the database is, and I don't know what Iscala is.

No surprise that you have long run times given the joins.

Consider LINKing the Iscala data source to MS Access, building out the query in Access, and using that as the data source, Access is much faster than Crystal when using disparate data sources.

-k