Business Object Interface

[wwvanselow]

I have a windows module that runs outside of MAS, that is run from a menu item we created inside of MAS.  Using the session object, I am able to get the UserName, Password, and CompanyCode to use with the Business Objects to login, but I am having trouble finding the UNC path to the server.

In one of our 200 client/server installations, which the client was run from the shared drive of the server Mas 200 folder, I noticed a item in the registry “HKEY_CURRENT_USER\Software\Sage Software\MAS 90 Business Desktop\Settings\MAS90RootDirectory”, that contains the proper UNC path to the MAS 200 server, that I can successfuly use to login using Business Objects.

But on another 200 client/server installation, which the client was installed from the disk, that same registry item contains a path that is a local path, which is not the UNC path to the server.  In this situation, do you know how the client knows the server path, and/or a place in the registry or a file this could be located that I get get to?

thanks,
Bill

[Gator]

What value do you have in:

HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\SOTAMAS90

That is the one that I usually use.

[wwvanselow]

On one of my client machines, that registry item is not there at all.  And on the other client, there is one there, but it has a "local" path, and not a unc path to the server.

[rolandc]

Uninstalling and reinstalling the MAS 200 client should do the trick. I always install from the UNC path similar to:

\\SERVER\Sage Software\MAS 200\Version4\MAS90\Wksetup\Wksetup.exe

If the clients have any "favorites" that were created in the toolbar or under My Tasks, they might be lost but I think you can backup and restore the text files MNUCBTN.TXT and MNUTASKS.INI if they exist in the client folder MAS90\Launcher\username before uninstalling.

After that, the registry keys should have the correct paths and your BOI apps should be able to read them.

[IBPIT]

The info MAS uses to connect to the server is stored in the sota.ini file stored on the local client.  If you have not modified the install path for the client, it is in C:\Program Files\Sage Software\MAS 200 Client\Version4\MAS90\Launcher.

[bretR]

Bill,

If you are after a UNC path to the MAS 200 installation on the server and if you are using the SY_Session object, we have a property set to the UNC path to the MAS90 folder as entered during workstation setup.

SY_Session.sPathCSRoot

Hope that helps

Bret