Sage 300 – Chopping Controls

Sage 300 provides various screens for entering and viewing enterprise/business data. Out of which many screens are well versed with the ability of resizing. Also Sage 300 stores the last screen dimension/preferences in the user folder *.ism files, so that the screen will be opened next time with the same dimension and preferences that the user used last time.

Though it’s a great feature it might be possible that due to this Sage 300 user may face the problem of screens getting chopped off for specific user. In this blog we are going to discuss on the resolution for this problem.

New Stuff : Quotation and Sales Order Report from Single UI

Sometimes the screen resolution has the effect on the sage 300 UI that some of it controls get chopped off. The steps to be followed in the resolving this user related issue is as follows.

It has something to do with user specific environment/preferences that Sage 300 stores for each user i.e. if you change the Dimensions of the screen and close it, next time when you launch the screen Sage 300 will use your last dimensions. You can verify following:

Sage 300 stores the last UI dimension’s/preferences user wise in the “.ism” file at the following path <Installation folder\Sage Software\Sage 300\USER\User_name\*.ism>.

Copy these “*.ism” to some Temp folder (just to be on the safe side) and then delete all these “*.ism” files under that users folder (as specified above), then try launching the screen in all the environments. Sage 300 will re-generate new ism files.

Note:

If the sage 300 ocx is customized, then first rename the *.ism files on the development machine, then again re-compile the ocx, and deploy in the Sage 300 installation folder.

For more information on this component you can drop us an email at accpac@greytrix.com

Also read:

1. Call .net Web service through OCX.
2. Customized OCX on Installation does not open up instead just a Status Bar comes up and stays
3. Error while setting up Database configuration for Sage 300 portal setup
4. Invalid Input. Cannot connect to the server. You may have specified as incorrect Server name or Server Port
5. Compilation Error for A4wFldEdtCtrl.dll fieldedit control