What is my problem

[Bill Neilsen]

I have a split database which I make constant changes to.
As a matter of course, I often rebuild the database i.e. open a blank
database and import everything into it. I do this to keep it clean and
operating smoothly.
However, recently I have developed a problem, I often get a message saying
that there isn't enough memory to perform the operation. Also, if I don't
regularly rebuild I occassionally get the same message as I make
modifications.
When I do the rebuild it imports the forms and reports quite quickly but has
developed a habit of being very slow to finally finish i.e. it just shows the
sand glass on the screen for quite a few minutes.
I'm using Windows XP with Office 2003 and my PC has 2G of memory.

Is it possible that memory is the problem or do I have a more sinister issue
I need to deal with.

 

[Jeff Boyce]

Bill

A split database usually means a front-end and a back-end. "I often rebuild
the database ..." could mean either the front-end or the back-end (or, I
suppose, both).

A standard configuration puts a copy of the front-end on each user's PC, all
users "sharing" a single copy of the back-end, located on a common/shared
LAN.

Does this describe your setup?

" ... to perform the operation ..." What operation? When do you get this
message?

More info, please...

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Jeff Boyce]

If the OPs original statement is accepted at face value, I suspect importing
the elements into a new (empty) database file periodically reduces the
size...

Regards

Jeff Boyce
Microsoft Office/Access MVP