Search results

OK, following your suggestions, I learned that the TILLDatabase variable is, in fact, Nothing. Somewhere in the midst of processing, TILLDatabase lost its value. Now I need to trace where this happened because it definitely should not be. The only place where I explicitly set it to Nothing is...

It is. It's a Public Dim It's used in multiple Subs and Functions throughout my app.

Dim TILLDatabase as Database

I put the breakpoint at the beginning of the sub. The error got thrown when I stepped into the DELETE statement.

Private Sub PhoneBook_Click() On Error GoTo ShowMeError ProgressMessages = ProgressMessages & "Updating Phone Directory." & vbCrLf: ProgressMessages.Requery TILLDataBase.Execute "DELETE tblPhoneDirectory.* from tblPhoneDirectory;", dbSeeChanges TILLDataBase.Execute "INSERT INTO...

This is an SQL statement executed within a VBA module. This statement has been executing without fail forever. It just started doing this today. I could understand if this happened because of a missing field, but a DELETE statement??

I come again to the Well of Knowledge... I have dealt with and resolved "Item not found in this collection" errors before. This is a new on me because it happens when the SQL statement "DELETE tbl.* from tbl" command. What would cause this on something as simple as a DELETE statement...

The DB has been compacted, repaired, then uncompiled and recompiled. Yes, everyone has their own copy of the front-end. I uninstalled and reinstalled Access Runtime 2016...no love. I even uninstalled Runtime and installed full Access 2016...still no love. I'm completely baffled.

This doesn't seem to be relevant. We're running Access 2016 (and 2016 runtime), legacy installation (not click-to-run), we are not a 365 shop. Our Access 2016 is fully patched.

Greetings to the well of knowledge... Posting this as a general question as I really don't think I'm dealing with a true corrupt query. I have an Access front-end to a back-end SQL Server DB. I make periodic updates to the front-end, on about an every-two-weeks basis. After the most recent...

So, for some Gawd awful reason, reinstalling Access fixed the problem. I have no idea why.

Greetings to the well of knowledge... This one has me gobsmacked. I have an Access 2016 front end with an SQL Server back end, with several reports, running on Windows 10 (fully updated). Some of these reports are landscape. All of my users, save one, get a landscape report when they print...

As noted above, I found the solution in another thread on the forum.

https://www.access-programmers.co.uk/forums/threads/query-to-return-most-recent-date.320449/

Actually, my DB is set up just as noted. I have a main "people" table that contains salient information about the donor (like name, address, basic demographics). The table I was alluding to is, in fact, a donations table. It contains the date of the donation, the date it was responded to...

Aaaaaand had I looked just below my post, I'd have found the answer. Sorry for clogging up the forum.

Greetings to the well of knowledge... I'm at a loss on this particular query design. We have a table of donors that contains the donor's name, the date of the donation, and the amount of the donation (among other fields). A user would like a list of all donors with the date and amount of the...

Nothing about this adds up. I'm thinking, as a low hanging fruit possible fix, uninstalling Access from her machine, running CCleaner to remove all remnants, then reinstalling it and see what happens.

That was my first thought. Insert key on or off, same bad behavior.

Additional info: Windows 10 20H2 Access 2016, fully patched.