"cannot open any more tables" in Access

From CCMDB Wiki
Jump to navigation Jump to search

Pagasa gets error "cannot open any more tables" in Access after doing a few things in CFE.

Short term fix is to exit and re-enter CFE.

No error, but cannot click any more

Resolved because this has not been reported again for several years and the cause was not identified at the time.

Trail for future recurrence: while assigning PseudoPHINs in CFE, the user reported that after repeated assignments the program showed a "cannot open" message, followed by runtime error 3014: "cannot open any more tables." Restarting CFE temporarily cleared the issue, but it recurred after more assignments, sometimes after fewer rows than before. The problem appeared during the clicking/assigning step in Generating PseudoPHINs, not in the related query, which was reported to work correctly.

If this happens again, treat it as a possible recurrence of the same issue and investigate CFE table/query objects being left open during repeated PseudoPHIN assignment.

Error "cannot open any more tables" in Access

Steps to reproduce:

  1. open CFE
  2. open PatientList
  3. run PL 2Phin Fake or Blank via dropdown
  4. do ~24 times:
    1. click handshake
    2. open record with binocs
    3. do usual corrections
    4. close handshake form

At some repetition, as the binocs on the handshake form are clicked, error "cannot open any more tables" appears. At that point, e.g. trying to assign another pseudophin will give that error again. Error happens all over until the program is re-started.

Work-around: Do a compact repair, this will allow you to work again and is quicker than going out and back in.

Observations:

  • This is probably not specific to pseudocodes, that is just the only query to routinely result in that many re-openings
  • The internet mentions this can happen when "set" statements aren't released, but I see no "set" statements as I step through this. Maybe the set statements happen from the handshake"

  • added: 2022-12-07
  • action: 2022-12-07
  • Cargo


  • Categories

Error "Enter Parameter Value"

The parameter value error usually means a query is opened from somewhere I did not expect it to be opened from, e.g. opening a form expects that it will be opened for a specific record.

  • Assigning Pseudo Phin or working on the queries if I worked long enough opened closed it then the error message pop up "Enter Parameter Value". PTorres 17:01, 2022 April 14 (CDT)
    • What is the specific action or button press after which this happens? I.e. which step in Generating PseudoPHINs? Ttenbergen 10:49, 2022 November 16 (CST)
      • When I click the pseudo button to the left of the PHIN field label, nothing is moving.PTorres 15:23, 2022 November 30 (CST)
        • I don't understand what you mean by that. What is the last thing you do before the "Enter Parameter Value" error happens? As in, what is the last button you click or last field you enter? Ttenbergen 12:15, 2022 December 7 (CST)
  • SMW


  • Cargo


  • Categories

Possible cause

Other sites mention this can happen when recordsets are opened but not closed and set to nothing repeatedly. I would need to find out exactly what step this fails at for Pagasa to know where this needs to be addressed.

Dead ends

This is not related to a known bug in MS Access: https://support.microsoft.com/en-us/office/access-is-unable-to-close-and-leaves-lockfile-active-b2dce32b-b8b0-41f1-ba40-7876e524d9da As of 2022-11-16 we are using "Version 1808 (Build 10392.20029 Click-to-Run)" which is a version before the buggy one.

Log