Search results for query: *

I have it working now. Thank You

Yes - I have it working now. I used DjangMan's suggestion.

Thank You - I will check out the links.

Thank You for your response. This is the code I currently have. 'create connection string sConnect = "Provider=SQLOLEDB;" & _ "Data Source=" & ServerName & ";" & _ "Initial Catalog=LMS_NYL;" & _ "Integrated Security=SSPI" 'create the...

...& "FROM #temp" sSQL = sSQL & vbCrLf sSQL = sSQL & "WHERE eff_thru_dte Is Not Null" sSQL = sSQL & vbCrLf sSQL = sSQL & "GROUP BY loan;" sSQL = sSQL & vbCrLf sSQL = sSQL & "select * from #LastIODate" sSQL = sSQL & vbCrLf sSQL = sSQL & "SET ANSI_WARNINGS ON" sSQL = sSQL &...

As always LB, thanks for your help. I had to do a couple of things. For formula1 I had to do what you mentioned and change loans to arLoans plus add global stringVar Array arMaster := ""; In formula2 I had to change the evaluation time to WhilePrintingRecords as well. Thanks p

I need to display, in group footer 1, loans from the detail section. In the detail section I can have more than one loan. Therefore, I set up an array to capture the loans. The problem I am having is that I need to reset the array for each group because without doing so I am going over the...

Lord I hate stupid issues. SQLDenis I finally figured it out. BTW - I put in editplus and did not see any hidden characters, but I decided to try something. Eventhough the len test showed the length to be equal I said why not just do a rtrim on p.loan. Guess what? That worked. UGH!!! I...

yeah that worked for me too...I give up

I know where you were going and was hoping they would have been different, but they were the same results.

SQLDenis when I put in what you provided above it works, but when I do the following select charindex(p.loan,rtrim(substring(p.loan_name,1,charindex('(',p.loan_name)-1))) from lmast p where p.loan = '3333333' and p.loan_name = PROP NAME 3333333 (NOTE F) it returns 0 same thing if I do...

using the statement charindex(PHIST.LOAN, p.loan_name)} and given phist.loan = 111111 p.loan_name = property name 111111 would return 15 but phist.loan = 222222 p.loan_name = property name 222222 (other text) would return 0 even though the loan is within the loan_name I cannot figure...

Hi Rosemary, I tried using charindex instead (select charindex(p.loan_name, PHIST."LOAN") from loanhist p where p.accounting_date = PHIST."ACCOUNTING_DATE" and p.loan = PHIST."LOAN") but received the same results - for some reason anything like loan_name = property name 787888...

Using Crystal 8.5 Any idea why using the statement {fn LOCATE(PHIST."LOAN", p.loan_name)} and given phist.loan = 111111 p.loan_name = property name 111111 would return 15 but phist.loan = 222222 p.loan_name = property name 222222 (other text) would return 0 - the loan is within the...

Well...partially solved. Where the loan_name field is like Boxes 123456, a value is returned, but for something like the example given above, Pottery 123456 (Note 1), 0 is returned. That has me baffled.

Problem solved, I had to flip the arguments around. Thanks

I have a SQL Expression that was not returning the result that I had expected so I broke it (the expression) down to test the locate function. When I did the test it was returning 0 for all values and that, I know for sure, is not correct. Anyone have any ideas what I may be doing wrong? FYI...

Thanks everyone. SQLSister, I will certainly give it a try. vongrunt - too funny. Actually, vongrunt, I think in addition to the standard that was being used, your point 1 was also occurring.

Well all this is what I did. I took the select statement of the code changed it to use the latest ANSI standard for the outer joins and it ran in 52 seconds. I let the programmer know this and he is going to incorporate into the stored procedure. We'll see how things go. I will keep you posted.

Here is something I found out about the using of the dbo on one of the objects. The programmer said, and I see this now, he is only using the dbo for the user defined table. He said when he originally coded the stored procedure, the user defined table was not working without specifying it as...