Splitting databases to get more gigabytes

[Lambi000]

I have a lot of Access databases going on for my employer, but now I've got a
proposal for one that will have 10,000 records. I always split my databases
(front end/back end) for multiple users, but I never thought that perhaps
that doubles my capacity until I read the specs for Access 2007. Does the BE
have 2 Gb available for records and the front end 2 Gb for forms, reports,
etc. in Access 2003? I can't see why not. Since we're not going to upgrade
anytime soon, I can sell them on this project if I can do that.

 

[Larry Daugherty]

That's correct.

 

[Lance]

Access won't even blink at 10,000 records. You're not going to be
approaching the size limit with that.

 

[John W. Vinson]

I have a lot of Access databases going on for my employer, but now I've got a
proposal for one that will have 10,000 records. I always split my databases
(front end/back end) for multiple users, but I never thought that perhaps
that doubles my capacity until I read the specs for Access 2007. Does the BE
have 2 Gb available for records and the front end 2 Gb for forms, reports,
etc. in Access 2003?

Yes. You can have multiple backends if need be.

I can't see why not. Since we're not going to upgrade
anytime soon, I can sell them on this project if I can do that.

Unless you're putting in enormous memo fields, 10000 records is TINY. Think
about it: an Access table record is limited to 2000 characters (exclusive of
memo fields). 10000 records x 2000 characters x 2 bytes/character (if you use
Unicode without compression, so this would be a worst case) = 40 *mega*bytes.
You're allowed 2000 megabytes!

I've got several tables in my current big app with well over 100,000 records,
and I know of working Access databases with 10,000,000 row tables. You have
nothing to worry about!