Re: Memory management problem?
- From: Tom van Stiphout <no.spam.tom7744@xxxxxxx>
- Date: Fri, 09 Jun 2006 07:10:02 -0700
On Fri, 09 Jun 2006 04:28:18 GMT, "Blaine Manyluk"
<bslaisne@xxxxxxxxxxxxx> wrote:
A few thoughts:
* The DevMode etc properties can be VERY tricky. The documentation is
not all that clear, and errors are more likely than elsewhere.
Eliminate that code for a while, and see if it makes a difference.
Also consider using Access 2002 or better, where the new Printer
object eliminates the need for them.
* Simplify the problem. For example rather than pulling the data from
Oracle, it could temporarily pull from local tables. That eliminates
an entire level of complexity.
* Run the app locally. Another simplification.
* Always run on latest service packs. I believe there is a SR-3 for
Office 2000, and there are service packs for Jet separately (SP8 I
think). Run Microsoft Update to exhaustion. The last thing you want is
bang your head against the wall and later find out MSFT fixed that
issue in a service pack.
* Run on another machine, preferably a virgin build with minimal
software installed. Printer drivers, video drivers, and fonts can be
corrupt or leaking memory.
-Tom.
Greetings...
I have some strange problems involving:
Access 2000 (9.0.4402 SR-1)
Windows 2000 Server 5.00.2195 Service Pack 4
Access apps with Oracle/ODBC back ends
One app is a reporting one, and it opens reports (in either
View or Print mode) from a master form. The code opens the
report first in Design mode, applies some changes to DevMode,
DevName, and Mip properties, then reopens the report for
View or Print. Any trouble happens on the last step.
The app usually runs fine for a while (2-5 reports), then
fails to open reports, and generates some strange error
messages:
2759 - The method you tried to invoke on an object failed
2455 - You entered an expression that has an invalid reference
to the property Inputparameters.
2465 - Access can't find the field "" referred to in your exp
2100 - the control or subform is too large for this location
? - The expression On Activate you entered as the event
property setting produced the following error:
Can't execute code in break mode.
? - Unknown Jet Error
All these point to "out of memory".
Note that even after this problem happens, I can still manually
open the reports all the time, and sometimes open them with
the master form and Devmode code. The app seldom crashes
completely, or needs to be closed and restarted.
I religiously repair and decompile all my apps. I haven't
(yet) done the laborious process of creating a new app, and
importing all objects, and relinking all ODBC tables. That
is my last resort. My code also sets objects to Nothing
when finished with them. None of these reports have large
image objects.
Another possibility is trouble with my Windows-level temp
directory. This app runs on a large server with huge amounts
of both RAM and disk space. Perhaps there is some setting
that I (and the server admin) have overlooked.
Any ideas?
- Blaine
======================================================================
[To reply, remove the S's from my address, and change the R's to N's.]
.
- Follow-Ups:
- Re: Memory management problem?
- From: Blaine Manyluk
- Re: Memory management problem?
- References:
- Memory management problem?
- From: Blaine Manyluk
- Memory management problem?
- Prev by Date: Re: Memory management problem?
- Next by Date: Re: Converting A2K to Access 03
- Previous by thread: Re: Memory management problem?
- Next by thread: Re: Memory management problem?
- Index(es):
Relevant Pages
|