G
Guest
First, sorry for a lengthy post - am trying to provide as much info as I can.
Am getting an error message in a new application I am trying to deploy -
"cannot open any more tables." Error code 3014 is displayed by the help
button, but the only reference to 3014 I have been able to find (even in the
MSDN Library) is related to printing issues (not the issue in my case). I
have never seen this before, and my pea-brain has exhausted searching for a
cause/solution...
Db info (Access 2003/split):
1) Each user will be running their own front-end (exclusive).
2) There is one particular form which accommodates the bulk of ongoing
activity in the db - bound to a single table, using an SQL statement rather
than a query in order to accommodate filtering by multiple fields.
3) The form uses a Tab Control, and the various tabs provide different views
of the filtered record(s) - like different pages of the displayed record.
4) On opening the form, it is set to show all records even though the Tab
Control is not visible until a filter is applied.
5) Some tabs have a subform embedded, bound to an additional single
updateable table (some do not).
6) Currently about 8,500 updateable records in the primary table; an equal
number of updateable records in two related tables. The remaining tables
involved only display various bits of static data, dependent on data in the
primary record(s) displayed.
My first trek revealed that Access specs indicate a limit of 2,048 open
tables. But, it also indicates "... the actual number may be less because of
tables opened internally by Microsoft Access." What does that mean (opened
internally), and where should it lead me?
One thought I have had is that perhaps because of the static data being
displayed that is dependent on the filtered record(s), Access may actually be
opening a number of recordsets (internally?) that is a multiple of the
records found?
Another thought... the form includes a 'Reset' button that turns the filter
off. As a result, the underlying SQL statement again shows all records.
My next thought was to figure out if there is a way to compact the db, each
time a user closes the form concerned (realizing it only compacts their open
front-end). Or, should that be done somehow in the On-Click event of the
Reset button? Can that even be done using code rather than the menu options?
Or... is there a different approach I should look for in somehow controlling
the number of open tables?
Any help, or pointing me to understanding the cause(s) and a solution is
MUCH APPRECIATED.
Am getting an error message in a new application I am trying to deploy -
"cannot open any more tables." Error code 3014 is displayed by the help
button, but the only reference to 3014 I have been able to find (even in the
MSDN Library) is related to printing issues (not the issue in my case). I
have never seen this before, and my pea-brain has exhausted searching for a
cause/solution...
Db info (Access 2003/split):
1) Each user will be running their own front-end (exclusive).
2) There is one particular form which accommodates the bulk of ongoing
activity in the db - bound to a single table, using an SQL statement rather
than a query in order to accommodate filtering by multiple fields.
3) The form uses a Tab Control, and the various tabs provide different views
of the filtered record(s) - like different pages of the displayed record.
4) On opening the form, it is set to show all records even though the Tab
Control is not visible until a filter is applied.
5) Some tabs have a subform embedded, bound to an additional single
updateable table (some do not).
6) Currently about 8,500 updateable records in the primary table; an equal
number of updateable records in two related tables. The remaining tables
involved only display various bits of static data, dependent on data in the
primary record(s) displayed.
My first trek revealed that Access specs indicate a limit of 2,048 open
tables. But, it also indicates "... the actual number may be less because of
tables opened internally by Microsoft Access." What does that mean (opened
internally), and where should it lead me?
One thought I have had is that perhaps because of the static data being
displayed that is dependent on the filtered record(s), Access may actually be
opening a number of recordsets (internally?) that is a multiple of the
records found?
Another thought... the form includes a 'Reset' button that turns the filter
off. As a result, the underlying SQL statement again shows all records.
My next thought was to figure out if there is a way to compact the db, each
time a user closes the form concerned (realizing it only compacts their open
front-end). Or, should that be done somehow in the On-Click event of the
Reset button? Can that even be done using code rather than the menu options?
Or... is there a different approach I should look for in somehow controlling
the number of open tables?
Any help, or pointing me to understanding the cause(s) and a solution is
MUCH APPRECIATED.