So it's not accurate to say that "the latest version of Logbook is slow." There's a cause for it. FWIW - I'm running Access on my main machine. and then it performs as well as Access can perform. we get them on a modern version of the 32-bit Access Runtime and give the MaxBufferSize a bigger chunk. The MaxBufferSize is low because Jet 2.x can't handle more than 2048. Most of the problems I see (as mentioned in the article) stem from the database using a driver that is part of the Jet 2.x engine from 20 years ago. our use of Microsoft Access is at the core of it all. If you're having problems with "slow", tell the tech support folks that I'll want to be involved. We don't charge people for fixing our software. (#3924 has nothing to do with slow) (from May 2020). It may be new to you, but I wrote this article months and months ago when there was another rash of these reports. If this were a known problem then (a) I wouldn't have fixed this several times recently by performing the changes to Access described in the article I referenced and (b) I would know about these "known issues" (given that all these folks work for me). please take a look at the process I describe in "The Problem with Microsoft Access". before you go writing product reviews on the Internet talking about how "HRD Logbook is slow". But fundamentally, we need to move to something else (SQLite or Microsoft SQL Server Express Edition). But Microsoft Access is old and it's not really a product that Microsoft has a lot of interest in these days. The DX cluster is WAY faster in the upcoming release. The changes we're making as we introduce the next release of Ham Radio Deluxe (that will include the "HRD Alert" feature) ended up eliminating half the work necessary for eliminating Access (sparing you all the details). and I've been very frustrated about this. It was - in fact - fixed by the process I describe in the "Problem with Microsoft Access" article. I called one of them and within about 15 minutes, I sorted it out. Two customers told me it was "freezing." So. I don't know if it's something in a Windows or Office update recently, but I've had a rash of customers reporting that Logbook is slow. this topic has given me a headache in the last week or so. I think I'm replying to the whole thread here.
0 Comments
Leave a Reply. |