We are having problems running Access 2000 under XP. I have run Access since the days of ver 2 and have never ran into the problems in previous versions. I do a lot of number crunching so my db's get up there in size but I have never lost one. but just today I was working way in one and got this message(again) ... invalid argument which from recent problems tells me exit the db cold boot the pc and go back in.. to get back as much of the ram as I can before the system crashes. I don't have this problem running under windows 98 with access 2000 just xp. any thoughts out there?
Thanks
Bill

What does your XP system have on it? Although MS states (http://support.microsoft.com/default...b;en-us;314865) you only need 64 megs of RAM (preferably 128), At home I have XP on XP and my system has 256 megs and I wouldn't go any lower as it can still be slow... At the office I use XP/XP and Access 2K with 512 megs of RAM. XP is especially slow when checking on properties.

Anyway, check your RAM & processor speeds and if needed, increase. When you upsize your OS, you usually need to add more RAM.

HTH,

Beth
PS I haven't had any of the errors arise which you are referencing and I've been using the Win XP OS with Access 2K and Access XP on the same system for over a year.

I don't know if this would be relevant to you, but as a follow up, MS also acknowledged and issue with Jet. Memory Use Climbs with Multiple Recordsets Under a Single Jet Session/Connection http://support.microsoft.com/default...b;EN-US;247140
"Microsoft Jet 4.0 is not releasing cached resources until the parent database connection is closed. Note that this is not a memory leak; rather, this is a resource allocation that is never freed until the parent object is closed."
You might also want to look at the "References" at the bottom of http://support.microsoft.com/default...b;en-us;239114
regarding Jet 4.0 SP7.

Regards,

Beth

I was wondering if you found a solution to your invalid argument problem. I am getting it now on updating my Access database. I have never had trouble updating before, but these are new tables, but can't imagine what I could have set up wrong. I have tried keyset, dynamic and static for cursor types. Nothing works, on my first update I keep getting that error with no specific code numbers. Very frustrating!!!!

Resistance is Futile!

Try to implement one of the solution.

http://support.microsoft.com/default...b;EN-US;835416