"Upgrade" from 5.0A Enterprise to 5.3 Corporate

[JeremyParr]

I am trying to move a customer from 5.0 to 5.3, the trick is, they are moving from Enterprise to Corporate. When trying to activate GL after the database has converted from 5.0 to 5.3, I get the following error:

Description: You cannot upgrade because some of the features you currently use are not available in the Corporate Edition. Data contains more than 1 budget set. Contact your Certified Consultant for the correct product to upgrade your General Ledger data.

Our ACCPAC support vendor has been working on this for a few days, and cannot seem to solve the problem. It sounds like a relatively simple issue, but an accpac specialist I am not. Anyone care to point me in the right direction?

 

[jayconverse]

Edit GLAFS and remove the extra budget sets.

Jay Converse
IT Director
Systemlink, Inc.

 

[ettienne]

To expand a bit on Jay's reply:
In the GLAFS table there is a fiscal set field, I cannot remember the exact field name, but it starts with something like FSDS*.
For Enterprise this field can have values 1 thru 5, A and Q.
The A is for Actual, Q is for Quantity, 1 thru 5 is for budget sets 1 thru 5.
In Corporate you are allowed only one budget set, so GLAFS may only contain records where the fiscal set field is either 1, A or Q. Any other records (2 thru 5) must be deleted from GLAFS.

 

[JeremyParr]

Makes sense. How do I edit the db directly? We are running Pervasive SQL

 

[jayconverse]

Use the Pervasive Control Center.

Jay Converse
IT Director
Systemlink, Inc.

 

[JeremyParr]

I ran a `SELECT * FROM "GLAFS" ORDER BY "GLAFS"."FSCSDSG"` and it returned over 11k rows. About a third had the value in the FSCSDSG column set to "1" and the rest were "A". None of the other columns had any simmilar looking data, so I assume this is the right place.

 

[jayconverse]

OK, then check GLO1, and see if CODELOCK2, 3, 4, and 5 are 1, and set them to 0.

Jay Converse
IT Director
Systemlink, Inc.

 

[JeremyParr]

None of the CODELOCK values in GL01 were set to 1.

 

[jayconverse]

If it was me, I'd Dbload your data into my Enterprise version, upgrade it there, then Dbdump it back into yours.

But try running Rvspy, that may pinpoint the table that it's complaining about.

Jay Converse
IT Director
Systemlink, Inc.