Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Trouble getting data on screen/linking tables

Status
Not open for further replies.

kimprogrammer

Programmer
Sep 15, 2008
160
CA
Hi
I started a thread and it was trying to get prompting done and after going back forth 25ish times I still couldn't get it to work - so I realy have to believe there something else confusing the issue.

So I started over - I just can't get this working in this report and it shouldn't be since this is not a difficult thing. So I appologize for this because i know I'm quite frustrated trying to figure this out and I'm sure the person helping me was as well.
-----
I created a new report from scratch because there has to be something else causeing the problem in this. So I'm keeping this simple going step by step
--------
I first created the command - it works well when dragged on the screen. I then deleted from the design page
I then created the prompt it works well only the divisions I want show up.
And all I have in the design page is the employee id from CPY10100. So when I run the report only the employees from that division are printed.
The Command is not on the screen!!
So so far so good.
But when I add in the swipeaccumulativehours file - is where I'm now having problems
----------------------
I have the command linked to nothing
CPY10100.PEmployeeClass --> CPY10050.PClass
the record select is:
({CPY10050.PClass} = {?Division} or {?Division} = "...ALL") //and
//{SwipeAccumulativeHours.PayCode} = "Comment"
-------------------
So now I'm trying to add in the swipeaccumulative hours
CPY10100.PEmployeeID --> SwipeAccumulativeHours.EmpNum
innerjoin
I take Paycode from SwipeAccumulative hours and put in in the detail.
So all that is on the detail is CPY10100.PemployeeId and SwipeAccumulativeHours.PayCode

I get one message - failed to retrieve data from database - then another - invalid arguement provide.
-------------------------------

If I reverse the link (which I believe is the the incorrect way of doing it)- I get fail to retrieve data from the database.

What could be the issue?




Thanks for the help
Kim
 
In your record selection formula, you show the reference to the Paycode commented out--is it in there or not? I think you need to compare the EmpNum from the swipe table to the EmplID from the other table. Try browsing each field by right clicking on each field in the linking expert. Notice the datatypes and also the lengths of the field.

Do all employees have hours in the swipe table? Are you sure "Comment" is a valid value for PayCode? Check the case in the data, also.

-LB
 
For now I have the reference to the paycode deleted. I want to keep this simple to try and understand how all this works together.

I'm not sure why I need to compare the CPY10100.PEmployeeID with the swipeAccumHours.empnum. If they are linked shouldn't they automatically come up?

But I did try it -
I put the following into the record select but I got the same results.(errors failed to retrieve data and invalid argument provided)
({CPY10050.PClass} = {?Division} or {?Division} = "...ALL") and
({CPY10100.PEmployeeID} = {SwipeAccumulativeHours.EmpNum})

-----------------------
I did the browsing field of CPY10100.PEmployeeID as there is data.

When I did it on SwipeAccumulativeHours.EmpNum nothing is there - but that makes sense because of the error failure to retrieve data.

Both data types say string and lenght of 15.

No not all the employees have data in the swipe file at this time - it still is in testing phase - but there are employees with data - but when I ask for a prompt I'm selecting "all" so I should see these come up.

In this case "comment" is a valid paytype code - technically it is not a paytype but in design we wanted the comments in the same file

But at this time I have it out of the record select - I'm would just be happy to see any paycodes being printed at this time.





Thanks for the help
Kim
 
I think you should do step by step troubleshooting. Place the three tables in the linking expert and link them, and place the empNum and EmployeeID and the two class fields on the report, and run it, to see if everything displays. Then add the PayCode field, and observe which values have "Comment" as the result. Then add the {?Division} parameter and create the record selection formula just using that. Select for "...ALL" once and select for a specific value. See when you get the error and then report back.

I would also verify that you have entered "...ALL" in your picklist so that it exactly matches the value in the record selection formula.

I am unclear whether you want to see all employees in the CPY10100 table regardless of whether they are in the swipe table.

-LB
 
I will try troubleshooting the way you sugested - even though I did the trouble shooting first but in reverse order.

But first i want to try something else - I spent a few days reading other posts with the error "invalid arguement provided". (Business Object doesn't even supply this error in their help).

Some taked about it being more of an ODBC issue - but I did come across one that their report work well but the ran it from another machine and received this error. They actually had to call Business Objects. But it was resolved by installing R2.

Thanks for the help
Kim
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top