Access:Memory/Install. Problem

My question: is there a tweak needed for Access 97 to run on my new system, since it has run fine on older platforms when installed from the same media?
Thanks in advance for suggestions.

Background:
I've just upgraded for the fifth time since first installing Access 97 from my OEM CD's. It's the second time in a row I've built on a bare-bones box, and the same OEM install of Windows 2000 Advanced Server (I use it on my desktop with only one old ThinkPad occasionally networked to it, same as previous installation). I have never had this problem with Access before. It will not get past the "out of memory/close programs" message at all.

System: P4, 1 GB physical memory (DDR) with ~700 MB available with the usual residents (anti-virus, firewall, ad filter, etc.) and Netscape loaded. 90 GB HD, with a 70 GB partition for Windows and programs inc. Access. Less than 10 GB is in use. OS is on Serv. Pk. 4 and current on patches.

I de-installed and re-installed Access, and that didn't help.

I tried various changes to VM/paging space and have closed all programs, but nothing helps. The previous computer was P2 with 20 GB HD and 512 MB memory...never a problem there. No problems on the earlier computers, either, with much less memory and swapping space. OS were W95, NT 4.0, and NT 3.51.

The rest of Office 97 works fine. Other apps work fine. I don't see anything in the system performance monitor tools or logs that indicates any issues with memory.

As far as I can remember, the problem is, that your computer has 1GB (or more) of RAM.

There's a knowledge base (?) article regarding this issue.

The solution was to install a newer version of microsoft jet.

have you installed all of the access 97 service packs?

You should be on atleast service release 2a.

If you cant get the access service pack the office 97 service releases & packs should update it.

Problem resolved, thanks to the two suggested remedies. I had not previously needed Office Service Pack 2.

I suspected memory size was the issue but didn't query the Knowledge Base well enough to turn up the solution there. As is so often the case, the best support comes from peers...thanks much, folks.