space limitation for MS Access front end application

  • Thread starter Thread starter iccsi
  • Start date Start date
I

iccsi

I have an application which space is 30 M for front end and about 600
M for back end database.
I know that the maximum space for MS Access is 2 G.

I got not enough memory please close other application message while I
continue to develop front end application.

I would like to know is it too big for a front end application which
is 30 M. If it is not then it is possible that my application has
memory leak.

Should I go to check memory leaks in the application?
If not then is it solution to split the front end in to 2?


Your information is great appreciated,
 
I have an application which space is 30 M for front end and about 600
M for back end database.
I know that the maximum space for MS Access is 2 G.

I got not enough memory please close other application message while I
continue to develop front end application.

I would like to know is it too big for a front end application which
is 30 M. If it is not then it is possible that my application has
memory leak.

Should I go to check memory leaks in the application?
If not then is it solution to split the front end in to 2?

Your information is great appreciated,

30 Meg seems a little large, have you done a compact and repair?
 
Yes, I do repair and compact before I deploy to users.
The size is after compact and repair.

It seems that I have to split it in to 2 or 3 for future enhancement,
Please let me know if I am wrong,

Thanks again,
 
iccsi said:
It seems that I have to split it in to 2
or 3 for future enhancement,
Please let me know if I am wrong,

I'm not sure what's going on, but 30 megabytes for an Access MDB or ACCDB is
not overly large. It's a long, long way from the 2GB size limit. And, as
that is not the problem you are facing, you are unlikely to gain anything by
splitting the front-end application database.

During development, especially, an Access front-end database can grow quite
fast -- remember Access does not automatically recover the space when an
object is deleted or replaced. It might be beneficial to compact and repair
more frequently in the development environment.

Larry Linson
Microsoft Office Access MVP
 
Back
Top