Pie chart based on two columns

[gem1204]

I need to create a pic chart based on two fields and I haven't been able to figure it out.
I have a field that shows the job number, Hours Completed, and hours remaining.
Here is my sql

SELECT [Job #] ,TimeCompleted,TimeRemaining FROM dbo_vw_ReleasedJobStatusTimeRemaining

When a user selects a job # I want to display a chart that shows a pie chart with one slice showing the timecompleted and the other showing the timeremaining.
I guess normally with a pie chart all the data comes from one field. In this case I have data in two fields so I'm not sure how to get the result I need.
Can someone please help me?
I'm using access 2010
Thanks

[June7]

Try using a UNION query to restructure the data. There is no wizard or designer for UNION, must type in the SQL View editor window of query designer.

SELECT [Job #], "Completed" As Category, TimeCompleted As TimeData FROM dbo_vw_ReleasedJobStatusTimeRemaining
UNION SELECT [Job #], "Remaining", TimeRemaining FROM dbo_vw_ReleasedJobStatusTimeRemaining;

Chart RowSource sql:
SELECT Category, TimeData FROM unionqueryname WHERE [Job #] = input criteria. Input criteria could be reference to report RecordSource field or textbox on report.

BTW, recommend no special characters (#, %, &, @, *, /, \), spaces, punctuation (underscore is exception) in names. Job # should be JobNum or Job_Num.

[gem1204]

Thanks!

I've already left work for the day but I'll give it a try tomorrow and let you know.

[Stingaway]

Pie charts threaten sanity in Access... Excel makes it look so easy.

[June7]

Yes, and I was going nuts until someone taught me about UNION query. All of my charts are based on UNION query. I know, I know, it's because my data isn't fully normalized. It's a compromise between normalization and ease of data entry/report design. Charting was the last feature in my project I learned.

[Stingaway]

I think I have used Union maybe three times for those times when you just couldn't do it any other way. As for the fully normalized part - I have created one (1) completely normalized database in my lifetime. It was perfect. So perfect it was pretty much unusable for end users... Especially those who did not understand why elements had to exist in a table in order to populate another table (or to be selected in a drop down for that matter...)

These days making it to fourth normal is high-class. Typically I find myself balanced in third dealing with exactly the same compromise you mentioned. Good to know that there are others out there struggling with 'normal' as well.