Search results

Your perseverance has paid off CJ, not all the fields were indexed. Initial form loading takes approx. 2 secs and thereafter, it's pretty much instantaneous. Brilliant, massive thanks 👏 @tvanstiphout - I should've checked other fields after you also mentioned indexing earlier in the thread 👍

Previously, the amount of data was since the last archive (start of 2022). I've whittled it down to 180 days as per above suggestion and although it's not ideal (approx 7 seconds), it is a bit more palatable until the hardware is upgraded. Thanks CJ

Pulls in data for visitors that haven't signed in for some considerable amount of time. I've played around and deleted the majority of the records and it now takes 4 seconds - sacrifices functionality for what is still sub-standard performance.

I give it a try - if I run the first query in the background, in theory it should pull in the second query more quickly. Perhaps an issue with Windows 8 or slower PC spec all round

Yes, re-linked and simply testing on the slow PC desktop. Queries are located in the front-end

I think so but I've used a third PC that doesn't and performance is similar

Data is usually on a network but it doesn't appear to be a contributing factor - placing the backend on the desktop doesn't make a difference. Removed order by and it reduced by approximately 2 seconds, good shout but performance remains very poor on this particular aspect

The slow PC is on a network but the speed doesn't improve when both the front and back end are moved to the desktop

1. Yes, Autonumber 2. Both queries based on same table, yes it has PK 3. See 1 4. It is now, took it down to approx 18 seconds, thanks 5. 8 year old PC, 8 GB RAM running on Windows 8.1 - I should've included in my original post that it works within a second on another PC, apologies. Just noted...

Made a fractional improvement but thanks for the suggestion

Hi, I've got an issue with a slow query. I'm using the MAX function in an initial query (detailed below) to obtain the highest VisitorSignInID - typically this completes within a second. Upon running the second query below to pull in additional field values from the underlying table with...