I agree that Access should be running on the client.  You don't run software
from the server.  If you do, I would guess that only one user can access it
at a time?  Are all your Microsoft Office Products installed that way?

In any case, 8 GIG of RAM is huge and I can't imagine you creating anything
in Access that would use even a tenth of that.  If the average user can run
access on their PC (which generally do not even have hardrives that big,
much less RAM) then you should never have a problem.

You should be able to open your database on your sever and see how much RAM
is free.  I'm certain it willnot be reduced much from the level available
prior to opening the database.

Rick B
Hey Doug --

Thanks for the reply.  Interestingly -- Access does run on
the server in this case as the software was loaded onto a
server.  Were you thinking that maybe MSAccess program was
loaded on the client and the .MDB file was on a server?
If that is the case then I understand what you're saying
however MSAccess was loaded onto a Server and has been
running on the server for the past 2-3 years.

Any other thoughts on maximum RAM utilized and is there a
limit?

Thanks again.

The RAM on the

message

kill

to

RAM

I believe the configuration you have is that while the Access files (exe's,
dll's, etc.) are residing on the server, Access is actually running on the
client. Unless, of course, you are actually using terminal services. Access
is simply not a server program and you can't turn it into one simply by
installing it on a server.
You can confirm this by checking task manager on both the client and server
when running an Access app  from a client.