Out of Memory

[Margie]

Recently, when I open my membership database I get
a "Microsoft Visual Basic" window that opens with the
error message "Out of Memory"
If I click OK, it opens a larger MVB window
entitled "Microsoft Visual Basic - Balitmore Woods Members
[Break]
When I close that window, yet another MVB window opens
saying "This command eill stop the debugging"
If I click OK, I an able to work on the database just fine.
I have XP professional, 256k memory and very little else
on the machine.
Can you help me get rid of these windows?

 

[Lynn Trapp]

Try Compiling the database to see if there are any errors

 

[Dirk Goldgar]

Recently, when I open my membership database I get
a "Microsoft Visual Basic" window that opens with the
error message "Out of Memory"
If I click OK, it opens a larger MVB window
entitled "Microsoft Visual Basic - Balitmore Woods Members
[Break]
When I close that window, yet another MVB window opens
saying "This command eill stop the debugging"
If I click OK, I an able to work on the database just fine.
I have XP professional, 256k memory and very little else
on the machine.
Can you help me get rid of these windows?

Do you have a whole bunch of code module windows open in the VB Editor?
If so, those windows may be chewing up all the available memory. In
that case, close them all except one, make a trivial change in that
one -- like typing a blank at the end of a line -- and then close that
one and (*important!*) click the Save button. That should save your
project state with the windows closed, so they don't eat up your
resources.

 

[Margie]

Sorry, but I am way dumber than you think. How do I know
if I "have a whole bunch of code module windows open in
the VB Editor"?

-----Original Message-----

Recently, when I open my membership database I get
a "Microsoft Visual Basic" window that opens with the
error message "Out of Memory"
If I click OK, it opens a larger MVB window
entitled "Microsoft Visual Basic - Balitmore Woods Members
[Break]
When I close that window, yet another MVB window opens
saying "This command eill stop the debugging"
If I click OK, I an able to work on the database just fine.
I have XP professional, 256k memory and very little else
on the machine.
Can you help me get rid of these windows?

Do you have a whole bunch of code module windows open in the VB Editor?
If so, those windows may be chewing up all the available memory. In
that case, close them all except one, make a trivial change in that
one -- like typing a blank at the end of a line -- and then close that
one and (*important!*) click the Save button. That should save your
project state with the windows closed, so they don't eat up your
resources.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)


.

 

[Dirk Goldgar]

Sorry, but I am way dumber than you think.
LOL

How do I know
if I "have a whole bunch of code module windows open in
the VB Editor"?

When you see the big window that is captioned "Microsoft Visual Basic -
Balitmore Woods Members", are there a lot of other windows open inside
that one, each of which has a caption like "Balitmore Woods Members -
<name of module> (Code)"? Those are the windows I'm talking about.

 

[Margie]

There is only one window captioned "Microsoft Visual
Basic - Balitmore Woods Members [Break]"

 

[Dirk Goldgar]

There is only one window captioned "Microsoft Visual
Basic - Balitmore Woods Members [Break]"

Really? Then I guess I'm barking up the wrong tree. Maybe it's the
result of some sort of corruption (that is, damage to the database
file). Try creating a new blank database and importing all objects from
the old one, using the File -> Get External Data -> Import... menu
option. See if the same problem manifests itself in the new database.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

 

[Margie]

You are a genius. I did what you said and so far so good.
Thank you!

-----Original Message-----

There is only one window captioned "Microsoft Visual
Basic - Balitmore Woods Members [Break]"

Really? Then I guess I'm barking up the wrong tree. Maybe it's the
result of some sort of corruption (that is, damage to the database
file). Try creating a new blank database and importing all objects from
the old one, using the File -> Get External Data -> Import... menu
option. See if the same problem manifests itself in the new database.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)



.

 

[Dirk Goldgar]

You are a genius. I did what you said and so far so good.
Thank you!

Terrific, Margie! You're welcome.