5.0 Upgrade

Yahoo Archive
1
Did you run the "System Management / Utilities / Database Conversions" in after logging into Vantage for the first time? I think you have to run #5460 - Reset DB Sequence Controls". I missed that step one time and it affected labor records big time. It's the very last step in the Install Instructions for 4.0 to 5.0.


Troy Funte
Liberty Electronics


----- Original Message -----
From: jackiemotz
To: vantage@yahoogroups.com
Sent: Monday, October 28, 2002 11:05 AM
Subject: [Vantage] 5.0 Upgrade


Hi we just upgraded from 4.0 to 5.0 this weekend and or course it can
never go smoothly. I am trying to enter an employee in data
collection and I get the error message joboper record has no-lock
status, update not allowed. this happens on any job number that I
enter. If anyone knows the fix to this I would appreciate it.


Yahoo! Groups Sponsor
ADVERTISEMENT




Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please goto: http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto: http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto: http://groups.yahoo.com/group/vantage/links

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.


[Non-text portions of this message have been removed]
2
Although we still do not have ODBC working (I'm waiting for after hours to
install the fixes), I thought I would report on how the 5.0 upgrade went for
us for those of you who have still not upgraded.

1.) I followed the instructions which I downloaded from epicor's website
and they were very thorough and easy-to-follow. We installed Vantage 5 on a
new server. The installation of Progress, Vantage, and the progress and
vantage latest patches on the server took about 2-1/2 hours. (including
doing the backup and restore of the 4.0 database). We also ran the index
build utility per the installation instructions. This took about 10 minutes
to run.

2.) Next we installed the admin client and did the schema changes. The
schema changes took about 15-20 minutes.

3.) Next we set up the Progress explorer tool. This was pretty quick,
maybe 15-20 minutes to set up.

4.) The data conversions came next, those took about 45 minutes - 1
hour.

5.) The most time consuming thing BY FAR, was updating every Report
Builder report to reference the new service name. This took me several
hours to go through each one and also to update the fields that changed.
Since we have three companies, most of our reports are in triplet, so I have
hundreds or user reports to go through. What a pain! For each one, I had
to go in and change the service name then save the report. Also, why in the
world was it necessary to change a bunch of the quantity fields by adding
'Our' in front of them, I don't know, but I had to change this in so many
places as well.

6.) I previewed each crystal report and then went into my existing
crystal reports and verified the databases. Haven't had any problem so far
with those, but it's only been 2 days. Something to note, if you are
running mutiple companies, reports are now listed per company. On 4.0, the
default report was the same for all companies. The reason this was an issue
for me, was when I changed the custom reports and verified them, I also
saved them as a new name in the new 5.0 directory. When I went back and
updated this as the default in one company, the other companies still had
errors. I had to go into each company and set it as the default. I like
this change, I just wasn't aware of it, so it did cause me a bit of
confusion at first.

7.) One thing I forgot to do is set up the authorization for the
purchasing buyers. Someone had pointed out that this had to be done, but I
forgot to do it. So, yesterday morning, all the purchasers were calling me
asking why they couldn't choose their own name as a buyer. So, don't forget
to do that when you upgrade to 5.0!

8.) Something that was not in the install instructions, but that you
MUST do, is follow the instructions from the support document 1304MPS. I
didn't have this document when I initally did the upgrade and we started
getting strange errors yesterday. When I called support, they sent me tat
document and after following it, all errors have gone away.

I can't think of anythign else right now. Hope this helps anyone who hasn't
upgraded yet.

-Sarah




[Non-text portions of this message have been removed]
3
Sarah wrote...
>>"5.) The most time consuming thing BY FAR, was updating every Report
Builder report to reference the new service name. This took me several
hours to go through each one and also to update the fields that changed.
Since we have three companies, most of our reports are in triplet, so I have
hundreds or user reports to go through. What a pain! For each one, I had
to go in and change the service name then save the report. Also, why in the
world was it necessary to change a bunch of the quantity fields by adding
'Our' in front of them, I don't know, but I had to change this in so many
places as well."

This is a good reason to have a test database and a spare secretary. For 5.0 (and now for 5.1), I gave the simple instructions to our receptionist to change all the report builder reports. It is MOSTLY simply a matter of typing in the new path for the database, and the new service name. There were perhaps a dozen reports that had field changes, but the receptionist just made not of those reports and went on to others. I changed the reports that had to me modified myself. This alone saved me several hours of work, and was able to be done before the conversion. I also had the receptionist modify the Custom Report Links so that they pointed to the new reports. This has to be done AFTER the conversion, of course.

Troy Funte
Liberty Electronics






[Non-text portions of this message have been removed]
4
This seems like a recurring pain in our backsides, so I called
support to find out if changing service names every time we upgrade
is necessary. Per Chris at Tech Support, it is not. Therefore, when
we get to the point of testing 5.1, I'm going to try using the old
service names and I shouldn't have to go through the torture of
changing all my reports. If someone else wants to try it before I
get to it, of course I'd like to hear how it turns out.

Good Luck,

Brian Stenglein
Clow Stamping Company

--- In vantage@y..., "Troy Funte" <tfunte@e...> wrote:
> Sarah wrote...
> >>"5.) The most time consuming thing BY FAR, was updating
every Report
> Builder report to reference the new service name. This took me
several
> hours to go through each one and also to update the fields that
changed.
> Since we have three companies, most of our reports are in triplet,
so I have
> hundreds or user reports to go through. What a pain! For each
one, I had
> to go in and change the service name then save the report. Also,
why in the
> world was it necessary to change a bunch of the quantity fields by
adding
> 'Our' in front of them, I don't know, but I had to change this in
so many
> places as well."
>
> This is a good reason to have a test database and a spare
secretary. For 5.0 (and now for 5.1), I gave the simple instructions
to our receptionist to change all the report builder reports. It is
MOSTLY simply a matter of typing in the new path for the database,
and the new service name. There were perhaps a dozen reports that
had field changes, but the receptionist just made not of those
reports and went on to others. I changed the reports that had to me
modified myself. This alone saved me several hours of work, and was
able to be done before the conversion. I also had the receptionist
modify the Custom Report Links so that they pointed to the new
reports. This has to be done AFTER the conversion, of course.
>
> Troy Funte
> Liberty Electronics
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
5
I think you would would want to uninstall the previous version before using the new one, which would mean having a big hassle if you had to go back again (if there was a glitch in the conversion). Otherwise it should work.
Not only the service name, but the mapped drive would have to be the same as well (or the physical path to the database).

Troy Funte
Liberty Electronics

----- Original Message -----
From: bstenglein@...
To: vantage@yahoogroups.com
Sent: Tuesday, November 06, 2001 1:10 PM
Subject: [Vantage] Re: 5.0 Upgrade-Service Names


This seems like a recurring pain in our backsides, so I called
support to find out if changing service names every time we upgrade
is necessary. Per Chris at Tech Support, it is not. Therefore, when
we get to the point of testing 5.1, I'm going to try using the old
service names and I shouldn't have to go through the torture of
changing all my reports. If someone else wants to try it before I
get to it, of course I'd like to hear how it turns out.

Good Luck,

Brian Stenglein
Clow Stamping Company

--- In vantage@y..., "Troy Funte" <tfunte@e...> wrote:
> Sarah wrote...
> >>"5.) The most time consuming thing BY FAR, was updating
every Report
> Builder report to reference the new service name. This took me
several
> hours to go through each one and also to update the fields that
changed.
> Since we have three companies, most of our reports are in triplet,
so I have
> hundreds or user reports to go through. What a pain! For each
one, I had
> to go in and change the service name then save the report. Also,
why in the
> world was it necessary to change a bunch of the quantity fields by
adding
> 'Our' in front of them, I don't know, but I had to change this in
so many
> places as well."
>
> This is a good reason to have a test database and a spare
secretary. For 5.0 (and now for 5.1), I gave the simple instructions
to our receptionist to change all the report builder reports. It is
MOSTLY simply a matter of typing in the new path for the database,
and the new service name. There were perhaps a dozen reports that
had field changes, but the receptionist just made not of those
reports and went on to others. I changed the reports that had to me
modified myself. This alone saved me several hours of work, and was
able to be done before the conversion. I also had the receptionist
modify the Custom Report Links so that they pointed to the new
reports. This has to be done AFTER the conversion, of course.
>
> Troy Funte
> Liberty Electronics
>
>
>
>
>
>
> [Non-text portions of this message have been removed]


Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please goto: http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto: http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto: http://groups.yahoo.com/group/vantage/links

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



[Non-text portions of this message have been removed]
6
I don't know if the mapped drive matters for these. You can set the
location in Report Builder to be "Db\vantage.db", so as long as the vantage
database is still called 'vantage' and still resides in the db folder, you
won't have to change anything there, no matter which drive is mapped.
Similarly, in 'Custom Report links' you can set the location to be
"ud\LibraryName.PRL" and as long as that folder doesn't change from version
to version you won't have to update those either.



[Non-text portions of this message have been removed]
7
Hmmm. Good point. I'll have our receptionist use that path when she does the upgrade on the RB reports for 5.1.

Troy Funte
Liberty Electronics


----- Original Message -----
From: sarah.vareschi@...
To: vantage@yahoogroups.com
Sent: Tuesday, November 06, 2001 4:37 PM
Subject: RE: [Vantage] Re: 5.0 Upgrade-Service Names


I don't know if the mapped drive matters for these. You can set the
location in Report Builder to be "Db\vantage.db", so as long as the vantage
database is still called 'vantage' and still resides in the db folder, you
won't have to change anything there, no matter which drive is mapped.
Similarly, in 'Custom Report links' you can set the location to be
"ud\LibraryName.PRL" and as long as that folder doesn't change from version
to version you won't have to update those either.



[Non-text portions of this message have been removed]


Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please goto: http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto: http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto: http://groups.yahoo.com/group/vantage/links

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



[Non-text portions of this message have been removed]
8
At 07:46 PM 11/6/2001 -0500, you wrote:
> I don't know if the mapped drive matters for these. You can set the
> location in Report Builder to be "Db\vantage.db", so as long as the vantage
> database is still called 'vantage' and still resides in the db folder, you

I just set them to plain old "vantage" in 4 & 5. I think the pathname is
only paid attention to if you're running stand-alone, like a self contained
notebook install. Also, Vantage over-rides the database connection (the
server and port number / name) so you really don't even need to change
that. As long as you're on an upgrade that doesn't change the DB name,
like 4 -> 5, you can get away with only updating the reports when you
happen to go back for updates.

> Similarly, in 'Custom Report links' you can set the location to be
> "ud\LibraryName.PRL" and as long as that folder doesn't change from

Yes, definitely! Be sure to use relative paths there, and in menu items,
and anywhere else. That way you won't have to change them if the drive
letter moves.

-Wayne
9
Hi we just upgraded from 4.0 to 5.0 this weekend and or course it can
never go smoothly. I am trying to enter an employee in data
collection and I get the error message joboper record has no-lock
status, update not allowed. this happens on any job number that I
enter. If anyone knows the fix to this I would appreciate it.