SSA (sage system administration) should NOT require admin access on the local machine
SSA (sage system administration) should NOT require admin access on the local machine as stated in the subject; the admin tool is installed using a "click-once"nstaller and so it installs against the users profile (and thus does not require admin ...
Guest
over 2 years ago
in Installation
0
Idea Accepted - Gauging Support
Click once seems a good idea however it is leading to longer installs & in the case of users using terminal services excessive disk space being used, i.e. Sage 200 occupies ~250MB for the client, if you have a terminal services site you end up...
Guest
over 8 years ago
in Installation
0
Idea Accepted - Gauging Support
Sage 200 Client - Restrict session permission to one session
It's currently possible for the same user to run the sage client application more than once - this takes up additional user licences and can also cause other issues
Saeed Malik
almost 6 years ago
in Installation
1
Idea Accepted - Gauging Support
To have a Validate All button on the 50 to 200 migration tool
When moving customers from 50 to 200, if a customer has a financials only dataset, it takes numerous clicks to go into each commercials and Project area and validate for no real good reason. It would save a bit of time to have a Validate all butto...
Guest
over 8 years ago
in Validate Data
0
Idea Accepted - Gauging Support
For the 50 200 migration tool to migrate the Ex Ref field
Currently when you migrate from Sage 50 to Sage 200, the reference and details field are migrated on the PL/SL transactions. However the ex ref value isn't migrated. It is lost in the ether. Can the migration tool be updated to migrate the ex ref ...
Guest
over 8 years ago
in Ex Ref / Migration Tool
0
Idea Accepted - Gauging Support
