JayTheGeek
MIS
Some times the little things are the most important...
This relates to Macola ES 360 (4.0.0.323) on MSSQL 2000. The client environment is on MS 2003 Terminal Server.
We have quite a few 'standard' layout changes that get done to the user screens. Up until now, I rely on line managers to set this up when a new employee/user first logs in.
Good examples of this are: The OE screen, where we move a couple of the columns around. And the Bin Master screen, where we add Bin Priority and Qty on Hand columns.
My question is where does Macola 'hide' these changes?
I am in the process of implementing a second Terminal Server and I don't want to put my users in the position of redoing all of these personal changes.
I would appreciate any help you folks can provide to include these modifications in my migration plan.
Regards,
Jay
This relates to Macola ES 360 (4.0.0.323) on MSSQL 2000. The client environment is on MS 2003 Terminal Server.
We have quite a few 'standard' layout changes that get done to the user screens. Up until now, I rely on line managers to set this up when a new employee/user first logs in.
Good examples of this are: The OE screen, where we move a couple of the columns around. And the Bin Master screen, where we add Bin Priority and Qty on Hand columns.
My question is where does Macola 'hide' these changes?
I am in the process of implementing a second Terminal Server and I don't want to put my users in the position of redoing all of these personal changes.
I would appreciate any help you folks can provide to include these modifications in my migration plan.
Regards,
Jay