If you use global object variables you can go through them and set them all to nothing. There are no 'Across the board' methods for that. (for example, putting rst fields into local variables, closing the recordset then working with the variables from there on.Īt the time you issue an 'Application.Quit' statement, (or just prior) is there an 'Across-the-board' way to see if there are any recordsets open, and if so issue a rst.close and set rst=Nothing statements then fire the 'Application.Quit' line? I try and exercise all due diligence to close a recordset as quickly as I can after using it. Last but not least: When did you last /decompile your MDB?
Here some links to knowledge base articles that are referencing to these bugs value property.īut as I mentioned I didn't see these bugs for years, maybe you found a new one. insted of ! to reference and also when you referenced to a checkbox in a form without explicitly referencing it's. It's important that all files are closed by the Close command.įinally I remember that this bug sometimes occured when you used. Then this can (but not reproduceable) happen.Īnother reason can be that you forgot to close a text file by code. Most common reason is that you don't distroy references to Jet objects that you are opening yourself. Once my Access app is closed and I execute a DoCmd.Quit on the mainįorms' exit button, 'msaccess.exe' still shows up as active in Windowsĭidn't see this bug a long time anymore.