Re: [MSAccessProfessionals] Error Out of Memory - How big is too BIG for MS Access?

I agree with Crystal on checking your object variables, but also, don't try to do too much with a single database. I've had students before who tried to run their entire business off of one single database, when in reality, it could have been split into multiple databases. Remember, the accounting people don't necessarily need the same information as the warehouse and shipping people, or the CEO. You can create multiple front-ends that access the same back-end data, and each one can be much more lightweight and compact. So keep that in mind; one single database doesn't have to run the whole operation.

And remember, you can make buttons on your main menu that can open the different databases. So, in case the shipping people do need to access the customer records, they can. But if it's not something they use on a daily basis, then don't try to pack all those features into a database that's not going to use them.

LLAP
RR

_._,_._,_

---

Groups.io Links:

You receive all messages sent to this group.

View/Reply Online (#116444) | Reply To Group | Reply To Sender | Mute This Topic | New Topic
Your Subscription | Contact Group Owner | Unsubscribe [sugeng.panjalu.access@blogger.com]

_._,_._,_