Downloads
Download updates to our software here.
Resources
Paper based resources in PDF format.
Knowledgebase
Diagnose and solve issues with your installation(s) of our software.
You are in support
Support Section
Article : KB0005
Why does the software crash/hang when I try to log on?
Sometimes a dialogue box may appear informing "ODBC login failed".
This happens because the DSN file has not been edited correctly.
To Fix
1. Identify which unit you having this problem with
2. Open up the DSN file in a text editor such as notepad. (The DSN file for Unit 1 is called dblink.dsn, the DSN file for Unit 2 is called unit2dblink.dsn, and the DSN file for Unit 3 is called unit3link.dsn). This usually can be found in the DATA directory of the installation.
3. Check that the last line in the file, where it says "DBQ=" reflects the location of the "biunit1.mdb" database.
4. If not, edit this line to reflect the location of the database.
Example
Here the file unit2dblink.dsn has been edited to reflect the location of the Unit 1 database. This has been done in order to use the data from the Unit 1 database, and hence not having to re-enter student data:
If this does not fix the problem
Check that the location of the database is a place where students have read/write access to.
Check that the path is pointing to the correct location of the mapped network drive (if you are using one) and it has the appropriate permissions.
If the students do have read/write access to the location of the database and the problem persists, then the DSN file has to be recreated. Click Here.
Windows 98 users will have to recreate the DSN files
If this does fix the problem, you may find an additional problem if you are running Windows 2000. See ODBC issue.
Return to Knowledgebase
Sometimes a dialogue box may appear informing "ODBC login failed".
This happens because the DSN file has not been edited correctly.
To Fix
1. Identify which unit you having this problem with
2. Open up the DSN file in a text editor such as notepad. (The DSN file for Unit 1 is called dblink.dsn, the DSN file for Unit 2 is called unit2dblink.dsn, and the DSN file for Unit 3 is called unit3link.dsn). This usually can be found in the DATA directory of the installation.
3. Check that the last line in the file, where it says "DBQ=" reflects the location of the "biunit1.mdb" database.
4. If not, edit this line to reflect the location of the database.
Example
Here the file unit2dblink.dsn has been edited to reflect the location of the Unit 1 database. This has been done in order to use the data from the Unit 1 database, and hence not having to re-enter student data:
If this does not fix the problem
Check that the location of the database is a place where students have read/write access to.
Check that the path is pointing to the correct location of the mapped network drive (if you are using one) and it has the appropriate permissions.
If the students do have read/write access to the location of the database and the problem persists, then the DSN file has to be recreated. Click Here.
Windows 98 users will have to recreate the DSN files
If this does fix the problem, you may find an additional problem if you are running Windows 2000. See ODBC issue.
Return to Knowledgebase