	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

06/26/2009 at 08:36AM PDT, ID: 24525484

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

7.4

Dynamic Variables in FROM clauses in SQR

Asked by AGenMIS in SQR, Oracle HCM, PeopleSoft, SQL Query Syntax, MS SQL Server

Tags: SQR, FROM, SQL, PeopleSoft, HRMS, ANSI

We are in the process of upgrading our PeopleSoft database platform from SQL Server 2000 to 2005. During our testing we ran into a problem with 2005 in that it requires the use of ANSI Standard Outer Joins but some of our custom SQRs use Non-ANSI standard joins.

When we made the necessary ANSI Standard changes to the programs we ran into errors from putting dynamic variables into the FROM clause of a Select statement. We want to avoid changing the compatibility level back to 8.0 so we need to get all of the queries using ANSI Standard Outer Joins. I'm getting the following errors when running the modified SQRs:

(SQR 1303) Error in SQL (perhaps missing &name after expression):
(SQR 1304) Check SELECT columns, expressions and 'where' clause for syntax.

The code that is referenced below is all in a Begin-Select statement and when the query is run in MS Query Analyzer it runs successfully.

View the Solution FREE for 30 Days

         
           
             1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:

           
           
             *********NON-ANSI STANDARD********************************
 
FROM   PS_LOCL_TX_TYP_TBL LTTT,
PS_PAY_TAX         TBAL,
WHERE  LTTT.STATE       =* TBAL.STATE	
 AND LTTT.LOCALITY    =* TBAL.LOCALITY
 AND LTTT.EFFDT       = (SELECT MAX(EFFDT)
                                          FROM PS_LOCL_TX_TYP_TBL 
                                          WHERE STATE    = LTTT.STATE
		             AND LOCALITY = LTTT.LOCALITY
                                          AND TAX_GRP_TYPE = LTTT.TAX_GRP_TYPE
                                          AND EFFDT   <= $AGLCLTAX_THRU_DT)
 
*********CONVERTED ANSI STANDARD*******************
FROM PS_PAY_TAX TBAL LEFT OUTER JOIN PS_LOCL_TX_TYP_TBL LTTT
 ON (TBAL.STATE        = LTTT.STATE
         AND TBAL.LOCALITY = LTTT.LOCALITY
        AND LTTT.EFFDT    = (SELECT MAX(EFFDT)
                                              FROM PS_LOCL_TX_TYP_TBL 
                                              WHERE STATE      = LTTT.STATE
                                              AND LOCALITY     = LTTT.LOCALITY
                                              AND TAX_GRP_TYPE = LTTT.TAX_GRP_TYPE
                                              AND EFFDT        <= $AGLCLTAX_THRU_DT))

           
         

20091111-EE-VQP-91 - Hierarchy / EE_QW_3_20080625

1. shorak3,500
1. srnar3,500
3. tshel3,000
4. cs97jjm32,500
5. rrjegan172,250
6. SQL_SE...2,150
7. reb732,120
8. dqmq2,080
9. angelIII2,000
9. Ernariash2,000
9. mlmcc2,000
9. CGLuttrell2,000
9. matthews...2,000
9. elburgundi...2,000
9. itsmein2,000
9. dhanushkad2,000
9. zelron222,000
9. Muhamma...2,000
9. r_guerreiro2,000
20. Sharath_...1,800
21. CRXIuser...1,500
21. rushbo1,500
23. natloz1,000
24. ezraa800
25. acperkins750

1. chrismc30,275
2. PFrog13,875
3. tshel12,475
4. shorak7,000
5. Yurich6,000
6. srnar5,500
7. cs97jjm35,000
8. PedroCGD4,350
9. dqmq4,080
10. jgv4,000
10. chapmandew4,000
12. angelIII3,000
12. rickchild3,000
14. BrandonG...2,780
15. jinesh_ka...2,750
16. EugeneZ2,600
17. Lowfatsp...2,500
18. rrjegan172,250
19. SQL_SE...2,150
20. reb732,120
21. Ernariash2,000
21. mlmcc2,000
21. rscowden2,000
21. apeter2,000
21. CGLuttrell2,000
21. dtodd2,000
21. adamsjs2,000
21. PATKIRSCH2,000
21. sjturner22,000
21. dbaduck2,000
21. matthews...2,000
21. sungenw...2,000
21. lappins2,000
21. elburgundi...2,000
21. whityum2,000
21. natoka2,000
21. itsmein2,000
21. CMYScott2,000
21. jaciesla2,000
21. dhanushkad2,000
21. zelron222,000
21. Muhamma...2,000
21. FourBeers2,000
21. r_guerreiro2,000

Dynamic Variables in FROM clauses in SQR

Asked by AGenMIS in SQR, Oracle HCM, PeopleSoft, SQL Query Syntax, MS SQL Server

Tags: SQR, FROM, SQL, PeopleSoft, HRMS, ANSI

About this solution