This page deals with questions received about our Who's-In? software that are not already covered in the troubleshooting section of the On-Line manual.

One of our NT WorkStation users (who has been running WHOS-IN for quite a while) is now experiencing an ''Overflow'' error and WHOS-IN fails to load.
This is a strange problem with an even stranger fix. We are still not sure exactly what is causing the error, however a negative value in the INI file may be the culprit. The cure is to go to the users WINDOWS (or WINNT) folder and delete the WHOS-IN.INI file. Restart WHOS-IN and the INI file will be recreated (using its default values). If this still fails, please email us.

From time to time, I switch PC's around in the office. When I do this I can't get Who's-In to recognize the new user. Whatever was on that machine as a user stays that way. The only way that I can figure out to fix this is to Delete the user, go to the new users machine and log in. It will then say, "It appears that you are a new user...".
There *is* an easier way... Go to the PC you wish to change the user on, and delete the WHOS-IN.INI file from the Windows folder. Start WHOS-IN and it will then ask for the users name. Alternatively, EDIT the user name in the INI file... ensuring you have the spelling exactly as it is in the database. 

Why are some of the dates in the 'Last Modified' field displayed as dd/mm/yy and others appear as mm/dd/yy ?
Some of the users have not defined the 'International' settings in 'Control Panel' to the correct country. If you are in Australia, and the dates are displayed as mm/dd/yy, then Windows is set for the USA. (This is the default for Windows.) Change your Country Settings in Windows (Control Panel / International section) to cure the problem.

I have a user who has left the company - how do I remove the 'default user' details from the PC ?
Go to the users WINDOWS folder & delete the WHOS-IN.INI file. Next time WHOS-IN is run it will ask for a new default user to be selected.

I'm trying to repair the database, but the Repair utility tells me there is someone connected even though all users have logged off. Why does this happen ?
This isn't actually a WHOS-IN problem, it's a server problem (and seems to happen more with Novell than NT). The server normally keeps track of which users are logged on, and which applications they have open. If someone crashes their machine (or simply switches it off) the server is supposed to remove the user from its internal list, however sometimes this does not happen, and the server thinks the user is still connected to one or more programs.

To fix this problem (NOVELL) you need to log in to the server as administrator. (Using  LOAD MONITOR for Novell in this example). LOAD MONITOR allows you to see which applications are open by which users. From there, you can disconnect them by highlighting the user and hitting the DEL key. NOTE: Doing so will disconnect the user from ALL open applications, not just WHOS-IN. you need to log in to the server as administrator. (Using  LOAD MONITOR for Novell in this example). LOAD MONITOR allows you to see which applications are open by which users. From there, you can disconnect them by highlighting the user and hitting the DEL key. NOTE: Doing so will disconnect the user from ALL open applications, not just WHOS-IN.

To fix this problem (WINDOWS NT) you need to log in to the server as administrator. (Using SERVER MONITOR for NT), and find which user has the WHOS-IN.MDB file open, then disconnect the user. We do not however have the exact steps required. If anyone can supply this information, please help us update this page by e-mailing us the info. Thanks.

I have one user who gets ''disk or network error'' when she tries to open Who's In.   It will work after five or six tries.   Any suggestions?
This error can occur if the user has a notebook and is not connected to the network when they boot up (WHOS-IN is trying to connect to a database which ''isn't there''. The solution is to move the WHOS-IN shortcut from their STARTUP folder to the desktop, and ask the user to only log in to WHOS-IN when they are actually connected.

Who's-In has been running fine, now suddenly it reports an INCOMPATIBLE DATABASE VERSION error ?
This error is mainly caused when someone upgrades to Access 7 (or Office 97). When this application is installed, it deletes the older version of several DLL's. Too bad we happen to be using them! Fix the problem by copying MSAJT200.DLL and VBDB300.DLL from the WHOS-IN folder on the server to the users WINDOWS/SYSTEM folder. Office 2000 may also cause this problem, however we have not as yet received an reports.

Can Windows 95b corrupt WHOS-IN databases ?
YES ! If you have recently upgraded your system to Windows 95b or purchased a new computer with this version of Windows already installed, you may be experiencing some database corruptions with our WHO'S-IN? software.

The symptom is that the computer keeps freezing and has to be rebooted (Ctrl+Alt+Del usually doesn't work). When you go back into our WHOS-IN, you may get a message saying that the system is corrupted in some way, and usually requires the administrator to rebuild the database.

To check your version of Windows 95, right-click on the 'My Computer' icon on the desktop and select 'Properties' from the menu. Under 'System' (on the 'General' tab) you will see the version of Windows on your machine. If it says '4.00.950 B', you need to take the following actions:

The problem appears to be in a new version of the VREDIR.VXD (Virtual Redirection Device Driver) file that comes with the 950b release. The work-around is to download a copy of an EARLIER VERSION of this file EARLIER VERSION of this file from Microsoft into your windows\system folder.

The replacement file, was located at the Microsoft site, however Microsoft has moved or deleted the file, so we have provided it here for you.  Download VREDRUPD.EXE

To correct the database corruption problems, ensure all users are logged OUT of WHO'S-IN? then use the REPAIR utility to correct the database corruption. If you have any problems doing this, please e-mail us, or, if you are in Australia, call us on (03) 9889-0572.

WHO'S-IN? is not the only product with this particular problem, (it applies to many programs using a database), however that does not make things any better. Microsoft has   apologized for this problem, but with the complexity of today's software it is inevitable that incompatiblities will arise occasionally. We would like to congratulate Microsoft on their prompt action to make a working version of the program available.

As we receive more questions they will be appended to this page.

Press the BACK button on your browser to return to the Tech Support page.