• - To install runtime in every local computer. 
  • Yes, this is recommended
• - To create a path to that folder, so I can run wrun32 everywhere.
  • I assume you mean each local computer has a shortcut pointing to the local installation of wrun32.exe - if so, Yes this is recommended. If not, please explain further
• - The client configuration file is still located in shared folder.
  • You can point to this config file using a UNC path, a mapped drive (which references a UNC path), OR you can use AcuServer remote notation:
    • <localpath>\\wrun32.exe -c @servername:<local-path-on-server>\\configfile program-name

• - To Launch the application with the active folder located in the shared folder, but running the wrun32.exe local instance
  • Not sure exactly what you mean, but a good approach would be for the config file to contain a CODE_PREFIX entry that points to the location(s) (on the server) where the object files reside - using AcuServer notation:
    • CODE_PREFIX @servername:<local-path-on-server>\\object-dir1 @servername:<local-path-on-server>\\object-dir2 ....etc...
  • Most importantly, the config file should contain a FILE_PREFIX entry pointing to the location(s) of the Vision data files using AcuServer notation:
    • FILE_PREFIX @servername:<local-path-on-server>\\data-dir1 @servername:<local-path-on-server>\\data-dir2 ....etc...

The choice of whether to use AcuServer for the config file or the object files isn't all that critical. If you prefer to use a mapped drive or UNC notation that's fine, although if you have AcuServer running, why not use it for consistency? For one thing, you no longer have to ensure the correct drive letters are mapped on each and every workstation. Plus with AcuServer, it can work with remote machines or machines that may not be joined to the Windows domain.

The most important thing, and where you get the most benefit from using AcuServer, is to use it to access your Vision data files. Make sure that AcuServer is running on the same physical server as the data files, and the paths to the data directories (using AcuServer notation) only refer to local, physical drives on the server (i.e. NOT mapped drives).

First, thanks for the answer.

'- To Launch the application with the active folder located in the shared folder, but running the wrun32.exe local instance'

 I mean that I run the application from the mapped drive but via the acuserve service. This way I think I won't need to change all my code refered to c$system, c$copy, etc., due that the active folder is still the same.