Sage 100

Besides SY_Activation, SY_Module, and SY_Company, where might the version of a module for a company be stored? Keeps telling us that SO is in 4.3 after running the conversion in 4.5. Manually changed it in SY_Activation and it says 4.5 on Company Maintenance. But when you go to get into Sales Order, tells you it's not converted.

SO_Options has a field for data version

I'm not sure this applies but when i ran into this problem I went back to the convert button and it fixed the problem.

do you have any enhancements? you might need to check with the developer if so

If you have any enhancements look at the CI_EnhancementActivation file.

I forgot to add SO_Options to my list. :-) We've run Convert about 5 times - we get the error about SY_ShippingQtyByItem being missing every now and then but we now know to copy it out before we try. We do have some new enhancements, but we were actually having this problem without installing them. But it won't hurt to check the CI_EA file, anyway. THANKS!

When I have encountered this I have gone through the Options files for all of the modules, including CI_Options.

What's the exact error message you receive?

When you enter Sales Order, it tells you the files for this module have not been converted.

What does the activity log show about the conversion? Does it say it completed?

Did you change the reg unlocking keys by any chance? If so did you get the mod new reg unlocking keys?

No change to reg keys. Won't know about the Activity Log until this afternoon.

Try rebooting the server and then converting again. I don't know what that does but worked for me once.

@haroldwestover - I tried to get a reboot in the midst of all of this and client had a fit and fell in it. Apparently it takes almost 2 hours to reboot - don't know how much this was exaggerated, but that's what he claims.

OK< then try this: In SO_Options, is Field 2 New System, blank? Should be ""N"". What about Field 111, Data Version

Thanks. Keep those cards and letters coming if any of you think of anything else - client and I are holding off until next week to start again. Luckily this is one of those rare LEISURELY upgrades.

Beth, when you get back to this. There is also a Sublevel that can trigger the conversion message - If I understand correctly the level and sublevel in SY_Module is compared to the level and sublevel in SY_Activation for the company. When those are different it triggers the conversion message.

Oh, hey, thanks, @DavidOverholt - we were guessing when we modified the SY_Activation file on the sub-level, so that's definitely something to check.

Sy0ctl file. Some orphan records may be in there. I had this situation to 4.4 from 4.30. The module had not been installed since 4.05 but was hiding out there.

OK, by using a combination of all of the above, we got it to work. We had used bits and pieces of lots of these, but this time we went down the list and made sure SY_Activation was 4.5, SO_Options was 4.5 and that we had to missing SO file in the folder. This time, it said nothing to convert and he was able to get into the screen and the DSD mods (which did their own little conversion and it worked, too). THANKS!

What a PITA!!! Time for a Miller...........

Tom Miller? Sorry.

I doubt if he tastes great or is less filling...............

Too funny!