Vantage 6.0 Problems

Thanks for the good info on problems with 6. We are working on
upgrading. As for your 2nd issue, are you sure those old Sales
Orders and Invoices are closed? I tried duplicating you issue and
while it does pause for a short while 15-30 seconds on average, it
does not process really old Order #'s or Invoice #'s. It only
processes those that are open.

Brian Stenglein

--- In vantage@yahoogroups.com, Cliff Drumeller <cliff@m...> wrote:
> We went live on Vantage 6 August 4. Here are a couple of problems
we are
> experiencing.
>
> 1)Credit Issues - Credit amounts on Companies with children
not
> calculating properly. Example we have one account with six children
that has
> a 3.5 mil credit limit. 1.1 mil outstanding and Vantage has them on
Credit
> Hold it somehow thinks they have 3.6 mil outstanding. Workaround is
to
> manually defeat the credit hold.
> 2)Credit calc's are slow - anywhere where Vantage recalcs the
credit
> limit - making a sales order it takes up to three minutes of
waiting before
> you can exit the screen. Accounting reports which access credit
limits are
> seeing them same thing. We are seeing it process 5 year old three
digit
> invoice numbers in the dialog box. We are up to five digit numbers
> presently.
> 3)Printing problems - Anyone who prints alot - Shipping,
Purchasing,
> quote, etc have been experiencing Vantage lockups (prowin32.exe
error
> followed by being booted out of Vantage). This I have cured by
doing a full
> RegEdit on these machines ripping out everything related to
Progress and
> Vantage then doing a re-install of Vantage 6. There are an amazing
number of
> registry entries left behind by the previous versions after
uninstalling.
> 4)Weird Progress.ini problem. Thirty days after live date
randomly
> people starting to not be able to run any RB reports from our
custom reports
> area - All 60+ of them in the menu would error out yet you could
run them
> from the machine next door or from RB on the affected machine. Once
a
> machine had this problem it had it forever. The it started
spreading like a
> virus. One on Monday, two on Tuesday, five on Wednesday. The cure
is to edit
> the Progress.ini on the server. You change the DLC and Probuild
lines to
> reflect the mapped drive instead of the physical drive and all the
problems
> go away. I still don't understand why it would effect a few
machines and
> start spreading.
>
> Cliff Drumeller
> Information Technology Manager
> Mass Precision Sheetmetal
> 408 954-0200 ex 217
We went live on Vantage 6 August 4. Here are a couple of problems we are
experiencing.

1)Credit Issues - Credit amounts on Companies with children not
calculating properly. Example we have one account with six children that has
a 3.5 mil credit limit. 1.1 mil outstanding and Vantage has them on Credit
Hold it somehow thinks they have 3.6 mil outstanding. Workaround is to
manually defeat the credit hold.
2)Credit calc's are slow - anywhere where Vantage recalcs the credit
limit - making a sales order it takes up to three minutes of waiting before
you can exit the screen. Accounting reports which access credit limits are
seeing them same thing. We are seeing it process 5 year old three digit
invoice numbers in the dialog box. We are up to five digit numbers
presently.
3)Printing problems - Anyone who prints alot - Shipping, Purchasing,
quote, etc have been experiencing Vantage lockups (prowin32.exe error
followed by being booted out of Vantage). This I have cured by doing a full
RegEdit on these machines ripping out everything related to Progress and
Vantage then doing a re-install of Vantage 6. There are an amazing number of
registry entries left behind by the previous versions after uninstalling.
4)Weird Progress.ini problem. Thirty days after live date randomly
people starting to not be able to run any RB reports from our custom reports
area - All 60+ of them in the menu would error out yet you could run them
from the machine next door or from RB on the affected machine. Once a
machine had this problem it had it forever. The it started spreading like a
virus. One on Monday, two on Tuesday, five on Wednesday. The cure is to edit
the Progress.ini on the server. You change the DLC and Probuild lines to
reflect the mapped drive instead of the physical drive and all the problems
go away. I still don't understand why it would effect a few machines and
start spreading.

Cliff Drumeller
Information Technology Manager
Mass Precision Sheetmetal
408 954-0200 ex 217