StarTracker FAQ StarTracker users have found this a useful educational prototyping tool. In order to support those loyal users, we will sponsor a moderated StarTracker discussion group. Stay tuned for subscription information. Q: What do I do with this dialog that pops up on my screen when I first open StarTracker? A: This is the OPTIONS Dialog. If this dialog appears when starting up the application, the registry entries are either missing or invalid. Before you can proceed to use StarTracker, you must set the following three options so that they are valid: 1) Local Report Path: StarTracker checks to see if it exists. If it does not, the characters will be in red. You can either change the local report path manually, or highlight the current report path and then move elsewhere on the form, and a path will automatically be created for you. The default is a subdirectory in your application directory called 'Query.' 2) The Workgroup security file, used by the metadatabase and also by Demo and Solo for user data. This file has the extension of .MDW. We supply one called iftime.mdw and it exists in your application directory. To run StarTracker this must NOT be replaced by another, but it may be moved or renamed. The filename will be checked to make sure it is present. If the name you give exists but the contents are bad, StarTracker will fail. 3) The metadata database. This is the database created by StarManager. It contains the family information that defines the relationships in your data that will then be used to run reports. This is also where 'Central' reports are stored. This file is a standard Jet V3.0 MDB as created by Access '95. When an MDB is chosen as the meta database, it must have been created by StarManager and is checked to make sure it contains at least one family. Q: Why cant I read my StarTracker CDROM? A:
You must be running Windows 95 with a 32-bit CDROM
driver, or Windows NT 4.0. Issue: We have
discovered an error in the install process for
StarTracker Pro. This error affects StarTracker Pro
distribution CDs bearing the volume label "STARTRACKER."
Those discs bearing the CD volume label "ST
Pro V1.1" are not affected.
This is the result of a Microsoft bug. A component,
"MSRDO32.DLL" does not get registered after
being placed (correctly) in This problem will result in error "424 Object required" when you start StarTracker Pro. If you have started and are running StarTracker Pro then you do not have this problem. Solution: To solve
this problem, you need to register this DLL. To do so,
choose "Run" from the Start menu, and type in
the command: Please note that this procedure will be needed whenever you install StarTracker Pro. Also, if you uninstall Office 95 or Office 97, the uninstall program removes DLLs that are required by StarTracker. Tested Configurations: Microsoft
SQL server Sybase
System 11 Informix
Workgroup Oracle 7
Workgroup Server Release 7.3.2.2.1 Known limitations 6.17.97 StarTracker (All):
StarTracker Solo:
StarTracker Pro:
StarManager:
The required DLLs and EXEs are: CTL3D32.DLL FileVer = 2.29. 0.0, ProdVer = 2.29, type = dll DAO3032.DLL FileVer = 3.0. 0.2504, ProdVer = 3.0, type = dll MFC40.DLL FileVer = 4.1. 0.6139, ProdVer = 4.1, type = dll MSJINT32.DLL FileVer = 3.0. 0.2504, ProdVer = 3.0, type = dll MSJT3032.DLL FileVer = 3.0. 0.2809, ProdVer = 3.0, type = dll MSJTER32.DLL FileVer = 3.0. 0.2504, ProdVer = 3.0, type = dll MSRD2X32.DLL FileVer = 3.0. 0.2504, ProdVer = 3.0, type = dll MSRDO32.DLL FileVer = 4.0. 29.26, ProdVer = 4.0, type = dll MSVCRT20.DLL FileVer = 2.11. 0.0, ProdVer = 2.10, type = dll MSVCRT40.DLL FileVer = 4.10. 0.6038, ProdVer = 4.10, type = dll MSWNG300.DLL FileVer = 3.0. 0.2504, ProdVer = 3.0, type = dll ODBCJI32.DLL FileVer = 3.40. 25.5, ProdVer = 3.40, type = dll ODBCJT32.DLL FileVer = 3.40. 28.29, ProdVer = 3.40, type = dll ODBCTL32.DLL FileVer = 3.40. 25.5, ProdVer = 3.40, type = dll OLEPRO32.DLL FileVer = 4.1. 0.6038, ProdVer = 4.1, type = dll VB40032.DLL FileVer = 4.0. 29.24, ProdVer = 4.0, type = dll VBAJET32.DLL FileVer = 2.0. 0.5924, ProdVer = 2.0, type = dll VBAR2232.DLL FileVer = 2.0. 0.5924, ProdVer = 2.0, type = dll VBDB32.DLL FileVer = 4.0. 29.8, ProdVer = 4.0, type = dll The required OCXs etc. are: COMCTL32.OCX FileVer = 5.0. 36.1, ProdVer = 5.0, type = dll COMDLG32.OCX FileVer = 5.0. 36.1, ProdVer = 5.0, type = dll SS32X25.OCX FileVer = 2.5. 0.20, ProdVer = 2.5, type = dll TABCTL32.OCX FileVer = 1.0. 23.0, ProdVer = 1.0, type = dll THREED32.OCX FileVer = 1.0. 41.0, ProdVer = 1.0, type = dll VSOCX32.OCX FileVer = 5.0. 3.5, ProdVer = 5.0, type = dll WREG.OCX FileVer = 1.6. 0.2, ProdVer = 1.6, type = dll Note: in a tabbed-folder display, if the contents of the tabs do not refresh properly when switching between tabs, the problem is most likely an incorrect version of TABCTL32.OCX. Version 1.0 of this control is actually a later version than some others with higher numbers, so the installation program may not replace these earlier, higher-numbered versions. If this problem occurs, you will have to replace this file in your system directory manually. Miscellaneous Issues:
|