Since installing SP3 on my XP Pro, Access 2003 , 2gb RAM set-up I've been getting into all sorts of problems with corrupted code and strange errors, such as "Out of memory". Reading through the forums, I'm wondering if the way I work might be the problem.
In the past I've run my app for testing and could go quite happily into the VBA editior to make changes while forms were open - but there was a suggestion on one of the posts that this may cause corruption - is that correct?
I've also read that incorrect references may cause corruption - they all seem to be there, but how can I check if they might cause a problem? Do they need to be in a particular order? This is how they are now:
2. Microsoft Access 11.0 Object Library
3. Microsoft DAO 3.6 Object Library
4. Microsoft Outlook 11.0 Object Library
5. Microsoft Scripting Runtime
One of the symptoms is that I'll get the "Out of memory" message, then when I go to edit the main form (which contains 5 sub-forms on tabs) it won't open - there's no error message, Access just doesn't do anything with it. Sometimes it will open but one of the sub-forms seems to have got corrupted and I have to delete it and import an older version from a back-up to get it functional again.
So far I've tried de-compilng and compacting & repairing, creating a new d/base and importing everything (seemed to work for a while) and also running "detect & repair" in Access.
Any ideas gratefully received.