M
Mr. Calico
Using a Microsoft Access combo box on a form to display a simple string
lookup in a SQL Server table with only ~30,000 rows seems to create a
critical memory leak in access. The key is based on a GUID column and bound
to an other GUID column on the recordset of the form and a simple lookup of a
50 character or less string is displayed in the box. The primary table has
about ~35,000 rows. Microsoft Access uses a large chunk of memory after each
form query to the database and also continues to use up the memory each time
to the user moves from record to record until no memory is left in the
machine. The program never frees this memory until you crash out of access
or you exit prior to crashing. Even exiting the access from does not release
the memory. I can not seem to find any information about this problem and
have tested the issue on many different computers and different SQL servers
recreating it many times with different test databases and clients. If there
is a known solution to this issue please advise. Thank you in advance.
Mr.C
lookup in a SQL Server table with only ~30,000 rows seems to create a
critical memory leak in access. The key is based on a GUID column and bound
to an other GUID column on the recordset of the form and a simple lookup of a
50 character or less string is displayed in the box. The primary table has
about ~35,000 rows. Microsoft Access uses a large chunk of memory after each
form query to the database and also continues to use up the memory each time
to the user moves from record to record until no memory is left in the
machine. The program never frees this memory until you crash out of access
or you exit prior to crashing. Even exiting the access from does not release
the memory. I can not seem to find any information about this problem and
have tested the issue on many different computers and different SQL servers
recreating it many times with different test databases and clients. If there
is a known solution to this issue please advise. Thank you in advance.
Mr.C