Bound Control on Access Form Causing High Memory Usage on SQL Server

I got about 50 Access users every day using the SQL Server
2000 database. At the end of the day, SQL Server always
ran out of the memory. Someone told me this is because of
the bound connection on the Access form causing the memory
leak. Is there a way to fix this problem without changing
my Access form design.not really.
acccess bound controls open numerous connections PER FORM.
this is not good.
only way to fix it would be to code your connectivity manually.
GAJ|||I currently have 2 GB physical memory which could last for
about 2 to 3 days if no one runs a big report. What if I
increase the memory size to 4 GB?

>--Original Message--
>not really.
>acccess bound controls open numerous connections PER FORM.
>this is not good.
>only way to fix it would be to code your connectivity
manually.
>
>GAJ
>
>.
>|||I suspect you will still eventually run out of connections and\or memory.
instead of using bound controls, write the code manually to populate
controls. that way you have explicit control over connection management.
will this work for you ?
GAJ|||Ken,
Are you sure it is really a memory leak? SQL Server will not release memory
once it grabs it unless the OS specifically calls for it. That is by
design. http://www.support.microsoft.com/?id=321363 Do you have things
other than sql server running on the same machine? If so you may want to
set your max memory setting to something less than the default of max and
see if that helps.
Andrew J. Kelly
SQL Server MVP
"Ken" <anonymous@.discussions.microsoft.com> wrote in message
news:bf6601c3ecfa$9f12e2a0$a401280a@.phx.gbl...
> I got about 50 Access users every day using the SQL Server
> 2000 database. At the end of the day, SQL Server always
> ran out of the memory. Someone told me this is because of
> the bound connection on the Access form causing the memory
> leak. Is there a way to fix this problem without changing
> my Access form design.