Are you using something like Wintask?
Rob Bucek
Manufacturing Engineer
PH: 715-284-5376 ext 311
FAX: 715-284-4084
<
http://www.dsmfg.com/>
(Click the logo to view our site)
________________________________
From:
vantage@yahoogroups.com [mailto:
vantage@yahoogroups.com] On Behalf
Of smithjennifer79
Sent: Wednesday, April 15, 2009 3:38 PM
To:
vantage@yahoogroups.com
Subject: [Vantage] Re: Vantage windows get slower over time... need
reopening.
I am sorry I don't have an answer to your problem. However, what I would
like to know how your using macros to enter data. This may be the answer
to a few of our problems.
Jen
jsmith@... <mailto:jsmith%40asmfab.com>
--- In
vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
"Kerry_Muntz" <kerry_muntz@...> wrote:
>
> PROBLEM:
> Vantage windows get sluggish and unresponsive after a thousand saves
or so. We'd like this NOT to occur.
>
> BACKGROUND:
> The average human won't ever encounter this problem... However we are
not an average company, and don't always use average humans to enter
data. We use a macros to modify mass data in Vantage (V8.03.405A), eg to
change primary bins for every part in Vantage using the Part Maintenance
windows. The macro reads data from a file, and opens the appropriate
parts, and goes through the motions like any human user of modifying the
part info - only quicker, and without coffee breaks... We use this macro
with other windows/modules too. Some windows exhibit this problem, some
do not.
>
> The problem we have is that after using a window a thousand times or
so, the window gets reaaaaaalllly slow, taking ages to draw/load data.
The macro can slow down to suit this, and/or reopen the Part Maintenance
window, which resolves the problem.
>
> BUT what I'd really like is to know why this is occurring, and avoid
the slow down. It seems like a memory leak, but traditional memory
management programs don't help. Officially our support company no longer
endorse our use of the macros (though they did when we were on V6), and
I expect that'd be Epicor's stand also (though we are not allowed to
talk to them directly anyway). V6 never had this problem.
>
> Any ideas? Is there some kind of caching happening that we can turn
off? Or is there some action we can perform to restore normal
operational speed?
>
> Thanks in advance.
>
[Non-text portions of this message have been removed]