Re: running report cause fatal error- on Win98, not XP
- From: "Riley" <CDStendel@xxxxxxxxxxx>
- Date: Mon, 27 Feb 2006 09:15:19 -0600
I know Win98 is a hog- they all are in their own way. The system it will be
running on is older (I perosnally think the thing should be escorted to the
dumpster, but that's another story) It has had memory upgrades, and I have
removed all the nonessential programs from it to free up hard drive space.
As well, there are very few items running in the background to conserve RAM,
so I'm not sure that it is an issue. It almost seems as even though the
program was written in Access2000 format using Access2003, there is
something that is carrying over from 2003 that 2000 does not like.
I've written things in the past for systms that were worse off than this
one, and haven't had a problem, but I was using Access2000 at the time
though too.
Thanks.
Riley
"Peter R. Fletcher" <seebelow@xxxxxxxxxxxx> wrote in message
news:mub0021uk18ua709198pe6psmsm45tuhsv@xxxxxxxxxx
In the (long ago!) days when I used Win 98, I used to see this sort of
problem relatively frequently. Access is a resource hog, and Win 98 is
both much less efficient in its use of physical resources (especially
memory) and much more prone to memory leaks than later versions of
Windows. It was not uncommon to have problems on Win98 developing or
running a database which would display no problems under Win 2000,
even on a machine with _less_ physical resources. If your problem is
related to this issue, and it certainly sounds like it to me, adding
more physical memory to the Win 98 system and/or making sure that
nothing else non-essential is occupying memory when you are running
the reports may help, but you may be snookered.
On Fri, 24 Feb 2006 15:06:04 -0600, "Riley" <CDStendel@xxxxxxxxxxx>
wrote:
I'm baffled on this one. I have written a Preventative maintenance
database
for our shop. I wrote it using Access2003 on my laptop. The computer
that
will be running it is older and running win98 and Office 2000. I wrote
the
database in Access 2000 format. The database runs 100% fine on my laptop
and the other computers that run XP in our office, BUT on the computer
that
will be running it (the older machine) I get a complete access crash when
I
try to run a couple of the reports. These are a couple of reports that are
generated by a pretty complex series of queries. Most of the reports are
fine, and print fine, but these more complex reports generate an error
popup
and Access shuts down.
I have NO idea where to start on this one, any help would be appreciated.
Like I said, the XP machines run it 100% fine.
Thanks in advance.
Riley
Please respond to the Newsgroup, so that others may benefit from the
exchange.
Peter R. Fletcher
.
- Follow-Ups:
- Re: running report cause fatal error- on Win98, not XP
- From: Peter R . Fletcher
- Re: running report cause fatal error- on Win98, not XP
- References:
- running report cause fatal error- on Win98, not XP
- From: Riley
- Re: running report cause fatal error- on Win98, not XP
- From: Peter R . Fletcher
- running report cause fatal error- on Win98, not XP
- Prev by Date: Re: running report cause fatal error- on Win98, not XP
- Next by Date: Re: running report cause fatal error- on Win98, not XP
- Previous by thread: Re: running report cause fatal error- on Win98, not XP
- Next by thread: Re: running report cause fatal error- on Win98, not XP
- Index(es):
Relevant Pages
|
