Welcome back! Ask questions, get answers, and join our large community of tax professionals.
cancel
Showing results for 
Search instead for 
Did you mean: 

2019 Lacerte 1040 - Interest Tab

TaxCPA18
Level 2

When moving through the different tabs (wages, dividends, Sch C etc.) the program moves relatively "quickly".  However, whenever you click on the interest tab the program does not respond, and if you click again the message "not responding" shows up on the screen.  Finally it opens that tab.  Anyone else having this problem?

0 Cheers

This discussion has been locked. No new contributions can be made. You may start a new discussion here

1 Solution

Accepted Solutions
TaxCPA18
Level 2

So the problem was with the Name Table in the Interest Screen.  Not sure if it was a particular name that was a problem, or just too many names in the table.  Once we deleted a number of names and cleaned up the list the problem went away.

 

View solution in original post

4 Comments 4
George4Tacks
Level 15

Is this just in one client, or in all. If just one client, I would suspect that there may be some corrupt input. Once in some screen, use Ctrl + W to enter the batch mode. Look carefully at the input for Screen 11. Examine each of the several entries. Look for any extra spacing or extra ASCII characters. Sometimes simply deleted a few entries, exiting the client, then doing the input again is quicker and safer.

 


Here's wishing you many Happy Returns
TaxCPA18
Level 2

No, it's not just one client.  Even in a client that hasn't been worked on yet you click on wages tab, it's fine.  Click on Interest tab..and then wait........ finally it opens.  

0 Cheers
George4Tacks
Level 15

Try the FORCE websetup, it often cures "weird" problems. https://proconnect.intuit.com/community/help-articles/help/how-to-perform-a-force-install-of-lacerte...

 


Here's wishing you many Happy Returns
TaxCPA18
Level 2

So the problem was with the Name Table in the Interest Screen.  Not sure if it was a particular name that was a problem, or just too many names in the table.  Once we deleted a number of names and cleaned up the list the problem went away.