Who's On?

	Membership:
	Latest: Chris Radcliffe
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5187

	People Online:
	Visitors: 349
	Members: 0
	Total: 349

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3288
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1351
Roger French	1311
mark.cook	1244

Use of OLEDB and other non-Lawson Data sources

Sort:

You are not authorized to post a reply.

Author

Messages

debika_sharma

Basic Member

Posts: 13

4/17/2008 3:49 PM

If you're using Lawson's OLE DB component to build reports in Crystal, can you also integrate data from other databases (non-Lawson) with the objects available in OLE DB? Basically can you join a database table from a non-Lawson database with a Lawson database table available in OLE DB?

John Henley

Senior Member

Posts: 3348

4/17/2008 4:50 PM

No, you would need to have multiple data sources within the Crystal Report (which you certainly can do...), but you cannot join within the OLE DB datasource to another database.

k-rock

Veteran Member

Posts: 142

4/18/2008 12:59 AM

and you would have to log in to both (or at least code the login to each source)

VinceD

New Member

Posts: 1

4/23/2008 7:06 PM

I was able to link an MS-Access data base to the Lawson OLE-DB tables.

Ruma Malhotra

Veteran Member

Posts: 412

4/23/2008 7:26 PM

Also Lawson has said in the past that will not support any issues of combining non-lawson tables outside lawson schema to lawson tables.

John Henley

Senior Member

Posts: 3348

4/23/2008 7:31 PM

That is true--you can create reports in Access as well as Crystal that combine data from Lawson (either via the OLEDB provider or a native ODBC connection, etc.) with non-Lawson data. However, your JOINs will not be done within the database--they will be done via Crystal or Access, which, depending on the data, can be a huge performance issue.

You are not authorized to post a reply.