Access eating memory 1

[Clawd]

While working in Access - mostly designing, testing and coding, my RAM (256 meg) is slowly being eaten up. After starting Access 2k, my RAM is usually around 80% free. After one to two hours I'm down to about 40% and the screen is freezing.

Is this an Access question or just another fun quirk of Windows?

Thanks,

Chris

 

[cmmrfrds]

Are you using windows 98? Is your access 2000 database converted from access 97?

 

[Clawd]

Cmmrfrds,

Let's see... yep (Win98 - 2nd edition) and nope (I'm pretty sure I started this one in 2K - I think). Dang this short term memory!!

Thanks

Chris

 

[Catadmin]

Clawd,

I'm sure you've already checked this, but it bears mentioning for those following this thread who don't already know. There are two Non-Access possibilities you might want to check first to be sure they aren't the cause of your woes.

First, check your memory cache/Temp Directory and trash all temp files (internet files, cookies, etc) which are cluttering up your hard drive. Make sure to Empty your Recycle bin after you and Explorer have had your "del" key fest. I have noticed that sometimes all those cookies, etc tend to cause problems in other applications because they are taking up so much memory and ram in the system that it makes running other apps hard, slow and a pain in the toosh.

If that doesn't help, get an updated virus scanner and check your system top to bottom. (Even check for fragmented drive space in Explorer. Sometimes that can screw you up too). Some of these self-propogating, but non-destructive, viruses can hide in your computer and start eating up memory when you activate certain applications. If one of your directories or folders has an inordinate amount of memory/space being used (IE, upwards of 100 MB) where it shouldn't have hardly any memory requirements, that could also be causing the problem.

It doesn't sound like it relates, I know, but I found out the hard way when a Desktop PC at my old job encountered that problem. We couldn't get anything to run and it turned out someone opened one of those Anna K. Virus emails and not only did it do the address book shimmy, but it hide on a directory which ended up stealing ALL of our availible memory not more then 2 hours after we started up the machine. But when we rebooted, things would be fine for a while. Getting rid of the virus and the cookies, etc. worked like a charm and our apps stopped "using" all this memory they were never actually using in the first place.

If that still doesn't resolve the problem, I leave it up to the Access Geniuses who have been at this longer then I have, because I'm not sure what the problem could be.

Catadmin - New to Server Admin, but willing to learn... All help is appreciated.

 

[cmmrfrds]

Clawd, I had a similar problem when I first went to Access 2k by converting an Access 97 app. On my Win 98 PC it kept eating up memory. I also had a PC with NT and didn't have the problem since NT manages memory better. What was happening is that the memory allocated for vba coding never got freed up. I found the problem on the Microsoft site but it was 2 years ago and I can't remember what it was called. To check for vba memory not being freed up go into a module or any vba code and check under windows on the menubar, if there are a lot of entries then this is probably happening.

Bottom line. To fix I had to make a new 2k app and import all my forms, tables, modules, and reports. This may not be the problem but the symtoms sure sound familar.

Jerry

 

[tunsarod]

I found that if FastFind is present in RAM then it'll slow things down. Hit Ctl/Alt Del and if FastFind is in the list highlight it and hit End Task.

Also remember to compact your ".mdb" files if you've been creating and deleting lots of forms and controls. They may not be visible but they are still in the system until you re-compact the database.

Rod

 

[Guest_imported]

Sorry I haven't thank yall for replying, I've been out of the country...back now and I do appreciate the suggestions.

I've tried them all but fast find so far.

I rid myself of cookies and temp files (veritable buttload). Virus check (updated) turned out ok. Ran AD-Aware program found one trojan horse (TSAD - came from PKZip). Still ate memory.

Now I'm building a smaller similiar program and monitoring that.

I'll compact that now and look for FindFast also.

Thanks again everyone,

PS. Got a new thread concerning trying to make pictures out of forms (for help file)

-Chris