Memory management problem?

**David W. Fenton** · Jun 9 '06, 01:55 PM

Re: Memory management problem?

"Blaine Manyluk" <bslaisne@corre ct.ab.ca> wrote in
news:CN6ig.2381 4$A8.22948@clgr ps12:
[color=blue]
> Access 2000 (9.0.4402 SR-1)
> Windows 2000 Server 5.00.2195 Service Pack 4
> Access apps with Oracle/ODBC back ends[/color]

[]
[color=blue]
> 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.[/color]

Where is the Access app being run? In Windows Terminal Server
sessions? Or on desktops? If on the desktops, then the server
configuration has zilch to do with it, but if on WTS, then you need
to look at the WTS settings. Perhaps you have insufficient RAM for
the number of simultaneous users involved.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

**Tom van Stiphout** · Jun 9 '06, 02:15 PM

Re: Memory management problem?

On Fri, 09 Jun 2006 04:28:18 GMT, "Blaine Manyluk"
<bslaisne@corre ct.ab.ca> 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.

[color=blue]
>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.]
>[/color]

**Blaine Manyluk** · Jun 11 '06, 06:35 PM

Re: Memory management problem?

"David W. Fenton" <XXXusenet@dfen ton.com.invalid > wrote in message
news:Xns97DD64E 826168f99a49ed1 d0c49c5bbb2@127 .0.0.1...[color=blue]
> "Blaine Manyluk" <bslaisne@corre ct.ab.ca> wrote in
> news:CN6ig.2381 4$A8.22948@clgr ps12:[/color]
[color=blue][color=green]
>> 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.[/color]
>
> Where is the Access app being run? In Windows Terminal Server
> sessions?[/color]

Citrix Server, which works much the same as WTS.
[color=blue]
> Or on desktops? If on the desktops, then the server
> configuration has zilch to do with it, but if on WTS,
> then you need to look at the WTS settings. Perhaps you
> have insufficient RAM for the number of simultaneous
> users involved.[/color]

I think so too. Could there be other Citrix-based settings
that need to be adjusted for Access?

- Blaine

=============== =============== =============== =============== ==========
[To reply, remove the S's from my address, and change the R's to N's.]

**Blaine Manyluk** · Jun 11 '06, 06:55 PM

Re: Memory management problem?

"Tom van Stiphout" <no.spam.tom774 4@cox.net> wrote in message
news:4ovi825jpc fq7lhe3168q4jlk gst7noadr@4ax.c om...[color=blue]
> On Fri, 09 Jun 2006 04:28:18 GMT, "Blaine Manyluk"
> <bslaisne@corre ct.ab.ca> wrote:
>
> A few thoughts:[/color]

Thank you.
[color=blue]
> * 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.[/color]

This client *needs* that code! :)
[color=blue]
> Also consider using Access 2002 or better, where the new Printer
> object eliminates the need for them.[/color]

This sounds like a very good idea. But I need to know:
- Conversion issues between A2K and A2002
- Reliability of new Printer object
(better than DevMode, but needs to be perfect)
[color=blue]
> * 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.[/color]

This is a large, complex, multi-user database with many
applications. All the apps are "locked" to read-only to
prevent bloating and corruption. (But this locking itself
might be the source of other problems. I really hope not.)

Local tables are hardly a practical solution. Perhaps if you
meant a temporary ADO cursor that resides in memory only not
in any files, databases or Access apps ... that might work?
Or even creating a temporary Access DB to use as a back end;
I did this to export to DBASE files while keeping the Access
app read-only.
[color=blue]
> * Run the app locally. Another simplification.[/color]

Running this system in its present form was a solution to
many other problems incurred by running it locally.
[color=blue]
> * 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.[/color]

OK, I'll suggest this.
[color=blue]
> * Run on another machine, preferably a virgin build with
> minimal software installed. Printer drivers, video drivers,
> and fonts can be corrupt or leaking memory.[/color]

As a test.

- Blaine

=============== =============== =============== =============== ==========
[To reply, remove the S's from my address, and change the R's to N's.]

**Tom van Stiphout** · Jun 11 '06, 07:45 PM

Re: Memory management problem?

On Sun, 11 Jun 2006 18:54:55 GMT, "Blaine Manyluk"
<bslaisne@corre ct.ab.ca> wrote:

All of my suggestions are temporary solutions aimed at narrowing down
where the problem is.
Upgrading to A2002 or 2003 is painless. Note that you can keep the
A2000 file format if you want. I don't know of any benefit not to.

-Tom.

[color=blue]
>"Tom van Stiphout" <no.spam.tom774 4@cox.net> wrote in message
>news:4ovi825jp cfq7lhe3168q4jl kgst7noadr@4ax. com...[color=green]
>> On Fri, 09 Jun 2006 04:28:18 GMT, "Blaine Manyluk"
>> <bslaisne@corre ct.ab.ca> wrote:
>>
>> A few thoughts:[/color]
>
>Thank you.
>[color=green]
>> * 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.[/color]
>
>This client *needs* that code! :)
>[color=green]
>> Also consider using Access 2002 or better, where the new Printer
>> object eliminates the need for them.[/color]
>
>This sounds like a very good idea. But I need to know:
>- Conversion issues between A2K and A2002
>- Reliability of new Printer object
> (better than DevMode, but needs to be perfect)
>[color=green]
>> * 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.[/color]
>
>This is a large, complex, multi-user database with many
>applications . All the apps are "locked" to read-only to
>prevent bloating and corruption. (But this locking itself
>might be the source of other problems. I really hope not.)
>
>Local tables are hardly a practical solution. Perhaps if you
>meant a temporary ADO cursor that resides in memory only not
>in any files, databases or Access apps ... that might work?
>Or even creating a temporary Access DB to use as a back end;
>I did this to export to DBASE files while keeping the Access
>app read-only.
>[color=green]
>> * Run the app locally. Another simplification.[/color]
>
>Running this system in its present form was a solution to
>many other problems incurred by running it locally.
>[color=green]
>> * 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.[/color]
>
>OK, I'll suggest this.
>[color=green]
>> * Run on another machine, preferably a virgin build with
>> minimal software installed. Printer drivers, video drivers,
>> and fonts can be corrupt or leaking memory.[/color]
>
>As a test.
>
>- Blaine
>
>============== =============== =============== =============== ===========
>[To reply, remove the S's from my address, and change the R's to N's.]
>[/color]

**David W. Fenton** · Jun 11 '06, 10:35 PM

Re: Memory management problem?

"Blaine Manyluk" <bslaisne@corre ct.ab.ca> wrote in
news:VnZig.4007 5$S61.8099@edtn ps90:
[color=blue]
>
> "David W. Fenton" <XXXusenet@dfen ton.com.invalid > wrote in message
> news:Xns97DD64E 826168f99a49ed1 d0c49c5bbb2@127 .0.0.1...[color=green]
>> "Blaine Manyluk" <bslaisne@corre ct.ab.ca> wrote in
>> news:CN6ig.2381 4$A8.22948@clgr ps12:[/color]
>[color=green][color=darkred]
>>> 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.[/color]
>>
>> Where is the Access app being run? In Windows Terminal Server
>> sessions?[/color]
>
> Citrix Server, which works much the same as WTS.[/color]

Is this a separate product, or a bunch of add-ins for Windows
Terminal Server? I thought that Microsoft had licensed the basic
Citrix technology and used it as the basis for WTS and Remote
Desktop, and that all Citrix provided now was a set of add-on tools
for use with WTS.

Have I misunderstood?

In any event, if you're mucking around with printer settings, that
may have a problem, since there's the issue of mapping the user's
local printer to be usable from the terminal session. In WTS, Win2K
didn't do this very well, but Win2K3 has made it transparent (as
long as an appropriate printer driver is installed on the WTS). In
NT 4 Server days, you had to buy Citrix extensions to get any
printer mapping, so maybe the Citrix product you are using provides
some different methods.
[color=blue][color=green]
>> Or on desktops? If on the desktops, then the server
>> configuration has zilch to do with it, but if on WTS,
>> then you need to look at the WTS settings. Perhaps you
>> have insufficient RAM for the number of simultaneous
>> users involved.[/color]
>
> I think so too. Could there be other Citrix-based settings
> that need to be adjusted for Access?[/color]

My only experience is with WTS in Win2K and Win2K Server. I've never
used any Citrix products.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

**Blaine Manyluk** · Jun 14 '06, 05:35 AM

Re: Memory management problem?

"David W. Fenton" <XXXusenet@dfen ton.com.invalid > wrote in message
news:Xns97DFBD7 BF5945f99a49ed1 d0c49c5bbb2@127 .0.0.1...[color=blue]
> "Blaine Manyluk" <bslaisne@corre ct.ab.ca> wrote in
> news:VnZig.4007 5$S61.8099@edtn ps90:[color=green]
>> "David W. Fenton" <XXXusenet@dfen ton.com.invalid > wrote in message
>> news:Xns97DD64E 826168f99a49ed1 d0c49c5bbb2@127 .0.0.1...[/color][/color]

[color=blue][color=green][color=darkred]
>>> Where is the Access app being run? In Windows Terminal Server
>>> sessions?[/color]
>>
>> Citrix Server, which works much the same as WTS.[/color]
>
> Is this a separate product, or a bunch of add-ins for Windows
> Terminal Server? I thought that Microsoft had licensed the basic
> Citrix technology and used it as the basis for WTS and Remote
> Desktop, and that all Citrix provided now was a set of add-on
> tools for use with WTS.[/color]

I do know the server is Citrix Server, and I connect to it with
Citrix Client. I'm not too sure of the exact relation between
Citrix and WTS; though my web research confirmed what you said.
[color=blue]
> Have I misunderstood?[/color]

It's Citrix.
[color=blue]
> In any event, if you're mucking around with printer settings,
> that may have a problem, since there's the issue of mapping
> the user's local printer to be usable from the terminal session.
> In WTS, Win2K didn't do this very well, but Win2K3 has made it
> transparent (as long as an appropriate printer driver is
> installed on the WTS). In NT 4 Server days, you had to buy
> Citrix extensions to get any printer mapping, so maybe the
> Citrix product you are using provides
> some different methods.[/color]

Could be.

Right now, I am going through all the reports in the apps and
setting their page setups to use Default printers. That might
make a difference; as I found out that the reports that had
the most trouble were the ones set to specific printers.
That seems to cause the most problems with the DevMode code.

- Blaine

=============== =============== =============== =============== ==========
[To reply, remove the S's from my address, and change the R's to N's.]

**Blaine Manyluk** · Jun 14 '06, 05:35 AM

Re: Memory management problem?

"Tom van Stiphout" <no.spam.tom774 4@cox.net> wrote in message
news:q7so82dmkq 4q2hs4imm2crols ebrkfaks8@4ax.c om...[color=blue]
> On Sun, 11 Jun 2006 18:54:55 GMT, "Blaine Manyluk"
> <bslaisne@corre ct.ab.ca> wrote:[/color]
[color=blue]
> All of my suggestions are temporary solutions aimed at
> narrowing down where the problem is.[/color]

I think I have a better idea of that now, but thank you
nevertheless. I did try creating a new DB, importing all
the objects, and manually re-linking all the ODBC tables.
That is a common solution for Access DB/app corruption,
but it didn't help.

(see my reply to David Fenton)
[color=blue]
> Upgrading to A2002 or 2003 is painless.[/color]

My client and I will have to do that, sooner or later.
[color=blue]
> Note that you can keep the A2000 file format if you want.
> I don't know of any benefit not to.[/color]

Question: If I use A2003, can I keep all my apps in A2K format,
but be able to use the Report object? Or is that feature
limited to A2K apps only?

- Blaine

=============== =============== =============== =============== ==========
[To reply, remove the S's from my address, and change the R's to N's.]

Memory management problem?

Memory management problem?

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment