Access version 2201 problem with laccdb

I had a similar problem after updating to Office 2108 14326.20738. When trying to close Access it would close the form and appear to be closing but then immediately re-open. It could only be closed by ending the process in Task Manager. The application is split into software in an Access front end linked to an Access or SQL backend. The application also uses two accdes as libraries holding further software. The only fix I found was to combine both the libraries into one accde. Access no longer seems able to handle the two library accdes. We had previously used this configuration for many years.

You need to close the database objects before setting the object to Nothing (I assume you mean "Nothing" rather than "Null"). Setting the object variable to Nothing releases the variable, but it doesn't actually close the object. You need to first close the object, and then set the variable to Null.

But you also need to make sure that the object exists before attempting to close it. Otherwise, it'll trigger an error.

The code I use (for a recordset object called "rs," for example) is this:

If Not rs Is Nothing Then rs.close



Set rs = Nothing

That should resolve your problem. And you should be using Execute rather than RunSQL.

In any case, I think that's a separate issue from what's being discussed in this thread.

Thanks nrgins... I am explicitly closing all recordset objects (before setting the variable to Nothing) but I'm not attempting to close the CurrentDB object ( I guess that it wont let me do that!!??)

As for your second point... I'm not sure that it is a completely separate issue... I am seeing both issues and to my mind... if Access is not closing connections properly it maybe that locks are being left in place too??

Yeah, there's some confusion here because I'm replying both to you and to PBallou.

And, yes, as I wrote in my second message to PBallou that's right. It does seem that it is related to this Access bug. If Access is not closing the databases, then eventually it will hit the limit.

It seems that applying the Trusted Location solution should work for you. Did you apply it to both the front end and the back end locations? Did you check the box to include subfolders? Seems to fix the problem for everyone else.

Many thanks Daniel

I've tried the trusted folder solution.. but it doesnt seem to make any difference.... I'm about to try and roll back by Office version

Thanks again

Phil

You need to close the database objects before setting the object to Nothing (I assume you mean "Nothing" rather than "Null"). Setting the object variable to Nothing releases the variable, but it doesn't actually close the object. You need to first close the object, and then set the variable to Null.

But you also need to make sure that the object exists before attempting to close it. Otherwise, it'll trigger an error.

The code I use (for a recordset object called "rs," for example) is this:

If Not rs Is Nothing Then rs.close



Set rs = Nothing

That should resolve your problem. And you should be using Execute rather than RunSQL.

In any case, I think that's a separate issue from what's being discussed in this thread.

Thanks nrgins... I am explicitly closing all recordset objects (before setting the variable to Nothing) but I'm not attempting to close the CurrentDB object ( I guess that it wont let me do that!!??)

As for your second point... I'm not sure that it is a completely separate issue... I am seeing both issues and to my mind... if Access is not closing connections properly it maybe that locks are being left in place too??