Sage 100

Attempting an upgrade from 3.71 to v4.4. Unfortunately, client loaded every module available back in the day. They only own six of them. I was successful in uninstalling every module but custom office and the .inquiry, .order and .store modules. These modules do anot appear in the uninstall module list. Does anyone know which system file I need to open in DFDM to remove the keys for these modules???????

pretty sure I did this on the sy0ctl

And that was the only file I needed (backup first)

Remember what the records looked like? It currently has 1,536 records. 10 plus years of crap has accumulated. I backed up the entire MAS folder as a precaution.

found it: In Windows Explorer, delete the ..\Mas90\Cm folder. In Sage MAS 90 or 200, open Library Master / Repair / Data File Display and Maintenance (DFDM), and select Sy0ctl.soa. Delete the [lC/M] ( l = ""ell""), and close DFDM. Run File / Run / SVMUPD to update the menus and remove Custom Office from Library Master Main menu. Note: SVMUPD rebuilds the LM Main menu based on the level records found in SY0CTL.

Yes I remember it being only one record and starting with lowercase i

I would advise you to NOT uninstall Custom Office because in an epic case of Catch-22 data conversion will fail if Custom Office is not installed even if you don't own it. The resolution being to install Custom Office although you can never go into it just so the data conversion goes through.

Now you tell me.....................

One down, one to go. No errors yet.

I had a similar situation with a client moving from 3.71 to 4.40 and dumping a third party vertical. They want to keep all of the history in 3.71 for the vertical. I couldn't do the migration with a module mismatch so I copied the entire MAS90 folder to a temp location and then used DFDM to edit the SY0CTL file in the temp location. The only record that made a difference was the [lW/M] (I thought it was a *one* and W/M was the module code) at the bottom of the SY0CTL file. I did not have to delete the data folders or remove the module through company maintenance.

Am doing an upgrade from 3.71 to 4.4 now and had to remove i (eye) record AND 1 (one) record as well. So removing iP/Z and 1P/Z (used by PM2000) did the trick.