Login
Welcome Guest! To enable all features please Login. New Registrations are disabled.

Notification

Icon
Error

Options
Go to last post Go to first unread
jgtr  
#1 Posted : Thursday, August 4, 2011 10:14:39 AM(UTC)
jgtr

Rank: Advanced Member

Posts: 63

I have now run across three instances where information on the SSG is different than the summary data on the Portfolio Summary Report. Here is a spacific instance for Honeywell:

  1. SSG say buy below 78.40; sell above 114.30
  2. Portfolio Summary says buy below 181.30; sell above 479.40
  3. the risk/reward does not agree
  4. the relative value is correct as is the current price
  5. there is only one listing for HON in my library

I had the same problem with another stock; however, the problem went away when I changed the forecast EPS. Both stocks are in the same portfolio. The third instance was similar, but in a different portfolio.

If it would help I can send screen prints of the SSG and Summary Report.

I am running TK6.4.2 on a PC

Jeff Traeger

 

Wanna join the discussion?! Login to your forum account. New Registrations are disabled.

gerlach  
#2 Posted : Friday, August 5, 2011 5:00:55 AM(UTC)
gerlach

Rank: Administration

Posts: 437

Thanks: 7 times
Was thanked: 14 time(s) in 10 post(s)
Are you making changes to the stock study but not saving them before you switch to the Portfolio Reports?

Is this happening right now? If so, can you send me a copy of your entire TK library so we can take a look?

Doug
jgtr  
#3 Posted : Monday, August 8, 2011 3:43:39 PM(UTC)
jgtr

Rank: Advanced Member

Posts: 63

I tried to send a copy of the entire TK stock file, but your file server continues to reject it. I suspect the file is too large. I have attached copies of the offending stocks that I am aware of.

I now have the problem with APA. The SSG says BUY below 86.90; sell above 161; the summary report says buy below 49 and sell above 25.40.

If the information is correct in the SSG it would seem to me that the data file is OK and that the problem is some where in the report generator. Should I un-install and re-install the program? If so will the authorization work for the re-install?

I'm at the point that I don't have any confidence in the reports. HELP!

 

Thanks.

 

Jeff Traeger

gerlach  
#4 Posted : Monday, August 8, 2011 4:04:55 PM(UTC)
gerlach

Rank: Administration

Posts: 437

Thanks: 7 times
Was thanked: 14 time(s) in 10 post(s)
I imported your three Toolkit files into mine, created a portfolio, and the prices match exactly what's on the Stock Studies. Do you have other studies for those companies in your library?

Doug
jgtr  
#5 Posted : Monday, August 8, 2011 4:27:09 PM(UTC)
jgtr

Rank: Advanced Member

Posts: 63

I just double checked. I have no duplicate files for those three stocks. It baffles me that the SSG's and the reports agree in 98% of the cases. I'd expect that if the problem was with the report generator that all the report buy/sell points would be wrong. I have multiple portfolios and so far it has occurred in two of the nine. Are there some tests I could run that would help daylight the problem?

What next?

Jeff
jgtr  
#6 Posted : Monday, August 8, 2011 5:07:10 PM(UTC)
jgtr

Rank: Advanced Member

Posts: 63

Doug,

Here is some more information using APA as a test: 1. re-ran the summary report and the same error occurred; 2. changed the low price from 5 yr low to forecast low; saved the change; ran the report and now the SSG and report agree on the buy/sell prices; 3. I changed the five year low back to the average five year low and this time the SSG and the report agree. So this appears to be an intermittent problem. I'm not having any computer problems.

Jeff
gerlach  
#7 Posted : Tuesday, August 9, 2011 5:36:09 AM(UTC)
gerlach

Rank: Administration

Posts: 437

Thanks: 7 times
Was thanked: 14 time(s) in 10 post(s)
We'll look into it. It seems like the Portfolio report isn't updating or displaying when you make changes to the stock study. I think that if you display the portfolio report, then make changes to an open stock study and view the report again, it won't update until you close and re-open the report.

Doug
jgtr  
#8 Posted : Tuesday, August 9, 2011 5:52:16 AM(UTC)
jgtr

Rank: Advanced Member

Posts: 63

Doug,

 

Just to clearify -regarding the test I ran: 1. I opened the ssg and noted the buy sell points and then closed it. 2. I opened the summary report, saw the error and then closed the report as well as the opening screen of the report section of TK6. I reopened the ssg, made the change to the low price, noted the new buy/sell prices and then closed the ssg. 3. I reopened the report and now the values matched. I re-cycled the same process, changing the low price back to the original value and the values in the report and ssg were still matching.

I just now ran another test. I updated the price file to see if that caused the error to re-occur - but it did not.

 

Jeff

jgtr  
#9 Posted : Tuesday, August 9, 2011 5:52:26 AM(UTC)
jgtr

Rank: Advanced Member

Posts: 63

Doug,

 

Just to clearify -regarding the test I ran: 1. I opened the ssg and noted the buy sell points and then closed it. 2. I opened the summary report, saw the error and then closed the report as well as the opening screen of the report section of TK6. I reopened the ssg, made the change to the low price, noted the new buy/sell prices and then closed the ssg. 3. I reopened the report and now the values matched. I re-cycled the same process, changing the low price back to the original value and the values in the report and ssg were still matching.

I just now ran another test. I updated the price file to see if that caused the error to re-occur - but it did not.

 

Jeff

Users browsing this topic
Guest (2)
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF.NET | YAF.NET © 2003-2024, Yet Another Forum.NET
This page was generated in 0.073 seconds.