If you are pushing 2GB in Access, you really need to look at migrating to something other than Access for the backend. Take a look at one of these.....
Even still, that shouldn't make that big of a difference.
I have an entire sub accounting system front end that is only about 10mb. It has graphics, and images to make more "pretty" and 10K+ lines of code as well as numerous forms, lots of queries and reports.
The backend is in SQL 2000, and the backend database is about 4gb right now, and growing daily.
Sorry to ramble, but I don't see how splitting the database would help the size a whole lot. Although I would agree that if it is not split, it should be done.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.