1. More RAM is better (always).
2. One approach I have seen work successfully is to put the tables (only) in a .mdb file on a server, and give each user their own .mdb file (or a compiled version) which LINKS to the data .mdb file using ODBC. This avoids having one station trying to both run the app and service the other users.
3. If you are executing an Access program on another machine, you can test for server slowness versus the importance of more memory fairly easily. Put the current fileon a server. With no other users running, start it from your machine, timing the startup. Disconnect. Now try it from another machine, and time it. If your machine is still significantly faster, memory is probably a big factor. Now move the file to one of the 64K machines. Start it locally and time it, disconnect, start it remotely from your machine and time it. Another test you might run is to have the file on your machine, start the program on another machine and time it, then start the program on a third machine and time it. Now disconnect both and try again, this time with you having the program running on your machine first. The timing difference on the third machine tells you how your machine is affecting the result.
Should you dump Access? Probably not. I have seen many multi-user full-enterprise accounting systems running on Access with no problems.
Should you simplify? Probably, especially if your controls have queries to populate pull-down lists. Consider that when youdo this, Access pulls some (possibly large) number of records across the wire to process your query (very fast locally, very ugly on a wan, moderately ugly on ethernet).
Good luck.