This is a known issue. What is happening is that when a user logs onto the server and launches Fundware, it is updating the TTY value in HKey_Local_Machine > Software > MicroFocus > 2.0 > Cobol > 2.0 > Environment to the newer user. If you are already logged into Fundware, your TTY number is being overwriten in the registry with the new users TTY number, thus you are getting import error reports that say something to the effect of "File not in system".

There are two work-arounds currently:

1) Rename the import file to the filename in the error report and re-import the file.

2) Run the settty.exe program from your WinKit (7.30) or Bin directories (7.31/7.40) and reset the TTY, then do your import again.