[AccessD] Access 97 Report problems

It may not be you but an OS level problem.  Windows itself can run out of
stack space.  Things like a bad device driver can also cause stack
overflows.

 What OS is the client?  If Win9x, have a look at this:

http://support.microsoft.com/default.aspx?scid=kb;en-us;149083

Jim Dettman
President,
Online Computer Services of WNY, Inc.
(315) 699-3443
jimdettman at earthlink.net

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Doug Murphy
Sent: Thursday, February 12, 2004 6:03 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Access 97 Report problems


Folks,

I have a database that has been running at a client site for some time
that has started having an interesting problem.  The background is that
when they ship an order three reports are printed, shipping invoice,
shipping document, and a core return slip if core items are involved.
This week all three computers using the system started giving an "Out of
stack space" message when the Core Return slip report was supposed to be
printed.  I looked at past threads on this plus a few articles on the MS
site.  The typical cause is a recursion that fills the stack or objects
not being closed.  Not the case here.  The report causing the problem
has no code and is based on a fairly simple query.

I can not re-create that problem on my Access 97 development machine,
which is ancient (Pentium 233) compared with the clients machines.  Mine
works fine.  We are running the same version, which is only a couple of
weeks old. I logged onto the clients machine through PCAnywhere and
tried opening the problem report in preview mode; it shut down Access
with no messages.  Did this several times and got the same result.
Thinking possibly I had a corrupted report I created a new report and
copied the objects over.  Still shut down Access when I ran it.

The one change at the client is they moved from a novel server to Win2k.
All other databases and this one except for this report seem to be
working fine so I don't' see that the conversion is the problem, but as
I have said before, I am not a network person.

Has anyone seen anything similar to this?  I am running out of things to
try.  The database was recently decompiled, recompiled and compacted to
get it's size down.  Every thing else is running fine.

Thanks in advance for any assistance.

Doug





_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com