shannonbirt
asked on
How to reduce Table Handles in Access forms
I have been having issues with 8 or so forms open concurrently and running into error 3048 in Access 2003.
I have been doing some research into error 3048 in access. Access cannot open any more databases and have found out about the 2048 concurrently open table handle limit.
I'm also aware that having a seperate FE and BE split doubles or triples the amount of open handles required, and do have a split FE and BE. I have had some luck in reducing this error message by tidying up code and closing any open references and by using closing and dereferencing objects.
One thing which i havn't been able to find out is if a combo box which has a query / table for its rowsource , does it require a seperate table connections / handles for each record the combo box is shown for ? or only once for the form the combo box is on ? If i knew this then i would know if its worthwhile to reduce the amount of combo boxes used.
As another part to this question is, as i undestand there is no way to accurately measure how many table handles are been used at any one time , short of duplicating the form and estimating that way. Is there a better way to monitor how many table handles have been used ?
I have been doing some research into error 3048 in access. Access cannot open any more databases and have found out about the 2048 concurrently open table handle limit.
I'm also aware that having a seperate FE and BE split doubles or triples the amount of open handles required, and do have a split FE and BE. I have had some luck in reducing this error message by tidying up code and closing any open references and by using closing and dereferencing objects.
One thing which i havn't been able to find out is if a combo box which has a query / table for its rowsource , does it require a seperate table connections / handles for each record the combo box is shown for ? or only once for the form the combo box is on ? If i knew this then i would know if its worthwhile to reduce the amount of combo boxes used.
As another part to this question is, as i undestand there is no way to accurately measure how many table handles are been used at any one time , short of duplicating the form and estimating that way. Is there a better way to monitor how many table handles have been used ?
you also need to consider your forms with several subforms.
domain aggregate functions in your queries are executed for every records.
domain aggregate functions in your queries are executed for every records.
ASKER
Capricorn I have everything closed and dereferenced in my code and i do not use domain aggregate functions any where. I'm trying to figure out what is expensive in terms of Table Handles and i know combo boxes can be expensive especially if they have joins etc in their queries. But if they effectively open a seperate connection for every record been viewed in a form , then they would be consuming a whole lot more table handles, than just once per form.
Obviously using less combo boxes is the aim , but i am down to the really necessary ones as they are required for user data entry to lookup other columns etc.
Obviously using less combo boxes is the aim , but i am down to the really necessary ones as they are required for user data entry to lookup other columns etc.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
shannonbirt,
<JDettman>
<I've always been told that it is one table reference per field that you are working with.>
...If this is true, then I just thought of something else.
Make sure your comboboxes have no more fields than is absolutely necessary. (Whether they are hidden or not)
I have seem people populate comboboxes with every field in a table, but thought they were OK, because they hid most of them.
HTH as well
Jeff Coachman
<JDettman>
<I've always been told that it is one table reference per field that you are working with.>
...If this is true, then I just thought of something else.
Make sure your comboboxes have no more fields than is absolutely necessary. (Whether they are hidden or not)
I have seem people populate comboboxes with every field in a table, but thought they were OK, because they hid most of them.
HTH as well
Jeff Coachman
you can test this by removing combo boxes until you don't get the error.
(do this in a back up copy)
if you are opening recordset, close them when not needed.
rs.close
set rs=nothing