Hello all, we finally upgraded our system so now our data is on a SQL
2000 database and our front end is on an Access 2000 database.
Everything's looking good so far, but there's this little issue that's
been bugging us ever since we upgraded.
Whenever anybody in our network opens the Access system and moves from
one form to another, the memory usage in their computer starts to climb
up. (Windows Task Manager > Processes tab). This keeps on going up
until we either close down the database OR (and here comes the weird
part) when we minimize Access. This has caused some other programs to
slow way down and affect the users' daily productivity. Sometimes the
memory used goes up to +68 KB and when we minimize Access, it goes back
to like 1.29 KB.
We're using unbound forms, we use store procedures and pass through
queries to access and edit our data. We have a User DSN Data Source
installed in every computer pointed to our server that has the SQL
Server 2000 database.
Does anyone knows if this is a known MS Access bug or is it our code?
Is there a way to replicate the way Windows XP acts when the MS Access
screens gets minimized and frees up all that memory so we can use it in
our code? We've tried a function to close all recordsets when exiting
a form, but that did seem not help at all.
Any help would be extremely appreciated.
Thanks and have a great weekend.
JR.
2000 database and our front end is on an Access 2000 database.
Everything's looking good so far, but there's this little issue that's
been bugging us ever since we upgraded.
Whenever anybody in our network opens the Access system and moves from
one form to another, the memory usage in their computer starts to climb
up. (Windows Task Manager > Processes tab). This keeps on going up
until we either close down the database OR (and here comes the weird
part) when we minimize Access. This has caused some other programs to
slow way down and affect the users' daily productivity. Sometimes the
memory used goes up to +68 KB and when we minimize Access, it goes back
to like 1.29 KB.
We're using unbound forms, we use store procedures and pass through
queries to access and edit our data. We have a User DSN Data Source
installed in every computer pointed to our server that has the SQL
Server 2000 database.
Does anyone knows if this is a known MS Access bug or is it our code?
Is there a way to replicate the way Windows XP acts when the MS Access
screens gets minimized and frees up all that memory so we can use it in
our code? We've tried a function to close all recordsets when exiting
a form, but that did seem not help at all.
Any help would be extremely appreciated.
Thanks and have a great weekend.
JR.
Comment