N
Nick
A database I've been deveoping for years and in use with 50 separate clients
has suddenly started generating error messages 'There isn't enough memory to
update the display. Close unneeded programs and try again'. The report
(uses MS Graph) does display Ok but I then get forms displaying with odd
fonts and white rather than the correct colour as background to the text in
labels or command buttons on an apparently random basis.
Needless to say there's plenty of memory. The problem manifests itself in
Access97 and Access2000 but not in Access2002 where I do the development work
(in Acess2000 format) and then convert backwards for those clients on earlier
versions. It's not confined to one PC, or even my office, and has occured on
Windows XP, 2000 and ME installations.
It also doesn't seem to be installation dependant as, if I go back 3
releases of the database, it seems to work Ok. Unfortunately a lot of
changes were made in the version where the problem looks to start so I'd like
to avoid going back to there and re-creating all the changes.
Creating a new database and importing everything across (whilst in a
client's office and on their PC) didn't help.
I remember having the problem many years ago and it went away but can't
remember what I did - old age is creeping up on me!
Has anyone any experience of this or any thoughts that might help?
has suddenly started generating error messages 'There isn't enough memory to
update the display. Close unneeded programs and try again'. The report
(uses MS Graph) does display Ok but I then get forms displaying with odd
fonts and white rather than the correct colour as background to the text in
labels or command buttons on an apparently random basis.
Needless to say there's plenty of memory. The problem manifests itself in
Access97 and Access2000 but not in Access2002 where I do the development work
(in Acess2000 format) and then convert backwards for those clients on earlier
versions. It's not confined to one PC, or even my office, and has occured on
Windows XP, 2000 and ME installations.
It also doesn't seem to be installation dependant as, if I go back 3
releases of the database, it seems to work Ok. Unfortunately a lot of
changes were made in the version where the problem looks to start so I'd like
to avoid going back to there and re-creating all the changes.
Creating a new database and importing everything across (whilst in a
client's office and on their PC) didn't help.
I remember having the problem many years ago and it went away but can't
remember what I did - old age is creeping up on me!
Has anyone any experience of this or any thoughts that might help?