The same thing happened with our database. I updated the Exports
table like Brad suggested and it worked. We are running a SQL Db with
multicompany. we had global BAQ's in 803.305 and i think that causes
a problem when upgrading to 403.
Thanks for the help Brad!
Daniel
table like Brad suggested and it worked. We are running a SQL Db with
multicompany. we had global BAQ's in 803.305 and i think that causes
a problem when upgrading to 403.
Thanks for the help Brad!
Daniel
--- In vantage@yahoogroups.com, "Brad Feazell" <Brad_feazell@...> wrote:
>
> Head's up in case someone runs into a problem with the 8.03.403a
> service pack and 8.03.403b patch we've seen on two of our systems.
> During the installation process, the conversion program 150 hung
> because values were missing in the GLBCOMPANY field in the EXPORTS
> table.
>
> The workaround was to kill the conversion routine, enter the company ID
> in the glbcompany field for all custom BAQs.
>
> The curious thing is that we entered the missing values to get through
> the 8.03.403a service pack but when we installed the 8.03.403b patch a
> couple of weeks later, the values had been erased and we had the same
> problem again. I'm pretty sure that we don't have any custom code that
> would erase these company ID values.
>
> Has anyone else run into this problem?
>
> Brad Feazell
>