Sage 100

Has anyone been getting reports that Sage 100 ""c"" is slower than non-c? I suspect its the myriad of other things (and not ""c"") that cause slowness but wanted to see what my peeps in the field are hearing.

I'm not sure there is anything specific to ""c"" that would cause slowness, since it is supposed to be the same code. Now, 100cloud may be another story.

It was mentioned during the Sage Guru session at MOTM and I wish I could recall exactly who brought it up, so it is evident with others. Can you list the version and is it standard theme or classic?

I had a client question this just last week.

Every version upgrade someone says the current is slower. For me it has not been strictly c. In some cases I think it is lack of AV fine tuning. We move to new folder, server and IT needs to exclude aggressive scans.

The version is 530.2 Standard. I appreciate the comment about AV issues & cloud but if all we did was update keys for ""c"" and not a move or new version + on premises install this would not seem to apply. Does anyone think that activation of the ""c"" features by keys update by itself could trigger slower performance? Does ""c"" alone make it slower?

Switching to ""c"" usually means the Standard Desktop (the new Launcher) is being used and some theme is being loaded . Since this is Standard, as a test you can revert 1 slow wkstn back to Classic Desktop and see if it runs faster.