I thought I had it fixed by adding a couple of helpful indexes, but no dice. Really, the tables it's dealing with are so small and the hardware so strong that the indexes shouldn't make a lot of difference. And it's not showing up on my reports as an "expensive" query.
I'd suspect that it's a purely HTML issue except that you can see it with a fast connection.
I'll revisit it from time to time to see what I can do about it. It's not really impeding anything, but it just kinda annoys me because I know it shouldn't be doing that.
Register for free to join our community of investors and share your ideas. You will also get access to streaming quotes, interactive charts, trades, portfolio, live options flow and more tools.