Database crashes during the process of development

[Lydia]

Hi,

I need to make continue changes to my database, like adding codes,
reformatting forms and subforms such as to make them taller or wider.

However Access frequently crashes poping up messages saying "there is not
enough memory" while what I did was adding a little bit code which usually
compiles and runs well and some times just after I changed the size of a sub
form.

The compact and repair usually takes care of the crash though not every
time. It is kind of annoying and scary. (My Access version is 2003.)

So far, the production database hasn't crashed since it has been in use;
however, I am kind of worried.

Any suggestion or recommendation to put me at ease?

Thanks.

Lydia

 

[Ken Snell \(MVP\)]

It's not uncommon for a database to "crash" if you're doing development work
on it. Various things that you do (such as editing VBA code while the form
is open in Form view) can cause this problem.

The solution is to make frequent backup copies of your database (I usually
make a copy after every individual change if it's just one, else after about
30 minutes of work in the database) and to compact/repair the database
often.

 

[Lydia]

Thanks.

I will continue do a good job at backing up my development.

Lydia
--
Access/VB Programmer

It's not uncommon for a database to "crash" if you're doing development work
on it. Various things that you do (such as editing VBA code while the form
is open in Form view) can cause this problem.

The solution is to make frequent backup copies of your database (I usually
make a copy after every individual change if it's just one, else after about
30 minutes of work in the database) and to compact/repair the database
often.