Who's On?

	Membership:
	Latest: jmc
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5210

	People Online:
	Visitors: 328
	Members: 0
	Total: 328

Name	Points
Greg Moeller	4184
David Williams	3349
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1377
Roger French	1315
mark.cook	1244
Chesca	1042

Crystal parameters - defaulting

4 Replies

0 Subscribed to this topic

23 Subscribed to this forum

Sort:

Author

Messages

Phil Simon

Veteran Member

Posts: 135

8/8/2007 6:24 PM

Hello

I was wondering if anyone figured out how to do this.

I have a parameter at the command level for PRTIME that will limit the records pulled, since that table gets to be big.

TR-DATE =?

To compare paychecks, I have another command set to PRTIME with the same parameters:

TR-DATE =?

Ideally, someone can put in parameter 1 = 7/1/07 and parameter s 7/15/07 so you can compare both paychecks.

However, OLEDB's command builder isn't liking adding the same parameter twice. The second one never appears in Crystal. I would think that you could do this.

Thank you,

ps

John Henley

Posts: 3364

New Poster

Engaged Reader

Avid Reader

8/8/2007 6:44 PM

Phil, are you using two different OLEDB/ADO commands in the report?

Phil Simon

Veteran Member

Posts: 135

8/8/2007 6:48 PM

Yes, I am using separate commands.

"Undocumented" feature?

John Henley

Posts: 3364

New Poster

Engaged Reader

Avid Reader

8/8/2007 7:28 PM

Not undocumented, just not well-understood.
I demonstrated it back in 2005 as a way to "JOIN" when Lawson doesn't support the join:
https://www.danalytics.co.../archive/2005-03.htm

Phil Simon

Veteran Member

Posts: 135

8/14/2007 6:54 PM

Thanks, John.

I was away from this one for a bit, focusing on little victories.

You're right; the order of the joins matters. Adding the table with the prompted date fields first, then doing a left OJ on the 2nd table, resulted in success!

You the man!