Suggestions on Memory Conservation

[Fred]

I realize that there are several variables here, but I'm I looking for suggestions on how I can save memory.

Here's the situation:
I created an application withe Access 2002 on a machine with a 2Ghz processor and 1G RAM, running XP Home Edition, saved in Access 2000 Format.
I took it to a machine with Access 2000, running Win 98 with 256MB RAM.
Early versions worked fine on the Win98 machine (just tables queries and reports).
The latest version added a switchboard and forms, and it runs out of memory quickly. If I change startup to skip the swithcboard and go directly to the main form, it lasts a little longer, but ultimately does the Win98/95 thing of tying itself in knots.
Assume that it is not possible to upgrade the OS and/or RAM.

1. are there Win98 memory mangement options I can try?
2. are there things I can do in Access to consume less memory?
3. are there any other suggestions?

Thanks.

 

[Adrian Jansen]

I would look carefully at the code for places where objects are created and
not destroyed, recordsets left open, etc. I have sucessfully run an Access
2000 app on Win95 with 48M of memory. 20 or so tables in the BE file, about
30 Mb, 100+ queries, 30-40 forms and reports in the FE file, around 15 Mb.
Was a bit slow, but never actually fell over.

--
Regards,

Adrian Jansen
J & K MicroSystems
Microcomputer solutions for industrial control

I realize that there are several variables here, but I'm I looking for

suggestions on how I can save memory.

Here's the situation:
I created an application withe Access 2002 on a machine with a 2Ghz

processor and 1G RAM, running XP Home Edition, saved in Access 2000 Format.

I took it to a machine with Access 2000, running Win 98 with 256MB RAM.
Early versions worked fine on the Win98 machine (just tables queries and reports).
The latest version added a switchboard and forms, and it runs out of

memory quickly. If I change startup to skip the swithcboard and go directly
to the main form, it lasts a little longer, but ultimately does the Win98/95
thing of tying itself in knots.

 

[Fred]

Adrian thanks. I don't know what happened to my last reply--must be another Microsoft mystery (it happens about 25% of the time).

I have no code. I do nothing unusual. This is a small application with 4 tables, 7 queries, 2 forms, and 3 switchboards. Very little data (126 humans in one table with related data in the others).

I'm shocked that 256MB is not enough. I suspect the video driver. Does anyone know a way to diagnose this?


----- Adrian Jansen wrote: -----

I would look carefully at the code for places where objects are created and
not destroyed, recordsets left open, etc. I have sucessfully run an Access
2000 app on Win95 with 48M of memory. 20 or so tables in the BE file, about
30 Mb, 100+ queries, 30-40 forms and reports in the FE file, around 15 Mb.
Was a bit slow, but never actually fell over.

--
Regards,

Adrian Jansen
J & K MicroSystems
Microcomputer solutions for industrial control

I realize that there are several variables here, but I'm I looking for

suggestions on how I can save memory.

I created an application withe Access 2002 on a machine with a 2Ghz

processor and 1G RAM, running XP Home Edition, saved in Access 2000 Format.

I took it to a machine with Access 2000, running Win 98 with 256MB RAM.
Early versions worked fine on the Win98 machine (just tables queries and reports).
The latest version added a switchboard and forms, and it runs out of

memory quickly. If I change startup to skip the swithcboard and go directly
to the main form, it lasts a little longer, but ultimately does the Win98/95
thing of tying itself in knots.

 

[Adrian Jansen]

Other than looking around in Task Manager to see what other processs are
running, and consuming memory, I dont know what else you can do. It should
not be an Access problem, if the app is that small.

--
Regards,

Adrian Jansen
J & K MicroSystems
Microcomputer solutions for industrial control

Adrian thanks. I don't know what happened to my last reply--must be

another Microsoft mystery (it happens about 25% of the time).

I have no code. I do nothing unusual. This is a small application with 4

tables, 7 queries, 2 forms, and 3 switchboards. Very little data (126 humans
in one table with related data in the others).

I'm shocked that 256MB is not enough. I suspect the video driver. Does

anyone know a way to diagnose this?