Memory consumption

[Guest]

I have a 3 y/o Dell running XP and I run an Access97 database. Recently
upgraded the memory on the Dell from the factory 256 to add a 512 from
Kingston based on the memory configurator from Dell (and verified my findings
using tigerdirect's memory configurator). All tools and applications worked
just fine with exception of Access97. Its error message advised not enough
memory (now it had been boosted from 256 to 768). The final solution was to
remove the older 256 and run with just the 512. However, Access often
seems to run slow. There are no properties where I can direct it to Run As
an older version of Windows compatible.

Advice would be appreciated. Do I need to hunt up a copy of a newer
Access and upgrade to that? If yes, are there any gotchas I need to be
aware of?

 

[Paul Shapiro]

You could check to see if Windows' page file is sized big enough for the
additional ram. MS recommends 1.5 times physical memory for the page file
size, or you can let Windows adjust it automatically. If the page file size
was fixed too small, maybe that could cause the Access error. I haven't seen
this, so I'm just guessing.

 

[Guest]

Good thought. I already did that, but will check on it again. We were
doing pretty well until the more recent automatic updates from Microsoft, so
I have no idea what's causing these problems. The USB printer is also very
very slow....acts as if there is no spooling process at all. Have tried
several different kinds of printers, although would love to find a good old
parallel port printer again to eliminate the USB problem.

 

[Tony Toews [MVP]]

I have a 3 y/o Dell running XP and I run an Access97 database. Recently
upgraded the memory on the Dell from the factory 256 to add a 512 from
Kingston based on the memory configurator from Dell (and verified my findings
using tigerdirect's memory configurator). All tools and applications worked
just fine with exception of Access97. Its error message advised not enough
memory (now it had been boosted from 256 to 768).

Interesting. This problem should only be happening when you have 1 Gb
of RAM or more. Never the less.

ACC: "Out of Memory" Error Starting Microsoft Access
http://support.microsoft.com/?kbid=161255

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Tony Toews [MVP]]

We were
doing pretty well until the more recent automatic updates from Microsoft, so
I have no idea what's causing these problems.

Note that the Automatic Updates do not cover Office 97 products. I
don't recall if they cover Office 2000.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Guest]

Tony, we are running with 512 not a Gb..... looks like the Jet Database
Engine update is a solution to look into..... I'm not familiar with it at
all, so will have my original Access CD handy in case I have to reinstall.
This is a database containing patient records for past 20+ years, so I
cannot jeopardize it......

I'll remember to post back here if this is a solution which helps us.