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 can’t I read my StarTracker CDROM? A: You must be running Windows 95 with a 32-bit CDROM driver, or Windows NT 4.0. This problem will occur if you try to read a CDROM under Windows 3.1 or Windows 95 with an old 16-bit CDROM driver, or Windows NT 3.51. 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 <windows directory>\system32. 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: "regsvr32 msrdo32.dll" Click OK. When this runs successfully you will get the message: "DllRegisterServer in msrdo32.dll succeeded" 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 version: 6.50 ODBC driver (SQL Server) company: Microsoft Corporation version: 2.65.0252 file: SQLSRV32.DLL date: 4/5/97 Sybase System 11 version: 10.0.3T4 ODBC driver company: Intersolv, Inc. version: 2.12.0000 file: SYSYBNT.DLL date: 8/22/96 Informix Workgroup version: 7.22.TC1 ODBC driver (Informix-CLI 2.5 32 bit) company: Intersolv, Inc. version: 2.12.0000 file: IVINF709.DLL date: 10/22/96 Oracle 7 Workgroup Server Release 7.3.2.2.1 version: 7.3.2.2.1 ODBC driver (Microsoft ODBC driver for Oracle) company: Microsoft Corporation version: 2.00.006325 file: MSORCLIO.DLL date: 1/11/97 Known limitations 6.17.97 StarTracker (All): Report display has a limit of 10,000 rows. Solo and Pro use the same set of registry settings and the same default install directory. When copying certain files from the StarTracker CDROM--namely user databases, local report files, and test metadatabases--these files will have the 'read-only' flag set. It is necessary for this file property to be cleared. Currently, modifications to groups and studies are committed to the database immediately. There is no confirming dialog or "undo" feature. Double-clicking on a group imposes constraints on all columns. These cross-column constraints will be represented in the constraint header. To remove a group from the constraint header, double-click on "all..." within the groups area of the dimension table on which you imposed the constraint. Groups that are saved into reports should not be deleted. As with groups, double-clicking on a study imposes constraints on all columns, and will be represented in the constraint header. However,the way to remove a study from the constraint header is to choose: Edit-->Remove study from report. No version checking between families and reports is done for locally stored reports. Drill Analysis does not allow the target report to be a centrally stored report. When running in 640 x 480 screen resolution, users may notice some truncation of messages in the StarTracker status bar. StarTracker Solo: There is currently no handling for security added to a customer's JET MDB, i.e. no user and password prompt. StarTracker Pro: This version can NOT be guaranteed to handle any database case sensitivity (database objects and reserved words). Do not provide a fully expanded path when defining the tables and fields in StarManager, e.g. in Oracle do not include the schema name. Please note Oracle's ODBC driver will not work. Field and Table identifiers have an imposed data length. Informix: 9 characters Oracle: 21 Characters Sybase: 21 Characters MS SQL: 21 Characters StarManager: This requires that Clusters, Families and Reports have unique names within the metadata database. Whatever the Group Table name is set to, StarTracker still assumes the table name is Name_GP. When defining a "Calculated field" as a measure in the Fact table, be careful not to include a <CR> in the text box for the formula. 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: The demo version contains references to test families and reports and can work against the 13 databases that are also available for download. The path to the databases must be a subdirectory of your application directory named 'Samples'. This version will NOT permit use of additional databases or families, and will not permit the use of different metadatabases or security MDW files. Note regarding Acrobat Reader: if you encounter text quality problems when printing Adobe Acrobat, use your printer's setup dialog to enable printing 'text as graphics'. This will force the use of Adobe's own internal scaleable fonts instead of printer fonts.