Another problem showed up with our website "upgrade" - I cannot login to Zapper. I enter my username/pwd as usual, hit "ok", and it just hangs there with the login screen forever. The app never starts.
I have to use task manager to kill it.
Ok, After I came back to my computer an hour laer, it did login! I thought I killed all the processes, but seems like one of them kept running somewhere, and finally logged me in. However, when I try to enter a typical date range for T Crb, it now hangs again "Loading data...", going on for abt 20 minutes now. It used to load star data in a few seconds before.
Something is wrong since the "upgrade".
Oh, it did finally come back with an error loading the data. See attached screen capture.
It doesn't sound like the problem is with Zapper so much as with intermittant server slowness. I will pass this on to my colleagues, but I'm afraid I can't offer any solutions at this point. With too much wait time, the connection to our server eventually breaks which is why I think you got the message about a problem with the query.
Having said that, I am planning to change the way Zapper accesses the database which (hopefully) will help a bit. Just have to find the time to get to that project...
Many thanks, Sara
I tried T CrB. It took 72 sec to search the database. It reported there were too many observations in the default JD range (2450000 - 2460000) so showed the first 20000 after I clicked ok. LC opened properly. I changed the start JD to 2455000 and it still took about 65 s. I have routinely waited about this long. Maybe a bit less? Not sure it is a lot longer than normal here? But, I tend to agree too long!
It would be nice for a few other previous users to try it!