Bugs and Work-a-rounds

Back to Table of Content
 

Auxiliary database can be destroyed if edited and the "Discard Current Changes" option is used. Some users make an auxiliary database to keep personal data for their own private use. They are made using the squadron database as the reference. With the squadron database select "File/Database Operations/Save Current DB As". The resulting new database can now be modified to suit the user. All current records can erased and new ones entered, a Christmas list for example. The new database can be edited and records added or deleted as required. The problem is that DB2000 doesn't make the companion backup file. This file is a copy of the database at the beginning of a session. It is used to replace the database being edited if "File/Discard Current Changes" is used. DB2000 uses the backup file for the squadron database instead wiping out the auxiliary. The same is true for the backup databases that DB2000 makes during the normal update process. But these are usually just used for reference and rarely edited. Work-around. 1. Make a copy of the auxiliary database and change the file extension from MDB to BAK. 2. Open the auxiliary database in DB2000. 3. Make a trivial change such as tagging a record and the select "File/Save Current Changes" This forces DB2000 to make the correct backup references and "File/Discard Current Changes" can be used for the current session. Steps 2 and 3 will be necessary for each new session.

Get message "DAO unable to initialize Jet Engine." User needs to install jet40sp3_comp.exe and mdac_typ.exe. See Downloads.

Changes to database elements are not reflected in RepWiz queries or reports. This issue stems from a bug recently introduced into DB2000 such that DB2000 was no longer updating the database timestamp prior to calling RepWiz. Because of this, RepWiz was not rebuilding the Enhanced Members table. This was fixed in DB2000 release 9.5.4. You can also use the RepWiz File menu to manually force the rebuilding of Enhanced Members.

MQSeries Returns an error code of 2538 We have only seen this error on DSL connections. Changing the connection option from "Never Hang Up" to "Always Hang Up" seems to correct this error.

MQ.DLL cannot be located. This is usually caused not by the MQ.DLL being actually missing, but by the MQ.DLL being unable to resolve all of its dependencies when it is loaded. The first thing you should do is to reboot your machine and see if that resolves the issue. If it doesn't, then proceed with the rest of these suggestions. Click on the ‘Start’ button on the lower left of your main desktop screen, then ‘Select Run’... Type in CMD and click OK This will open a DOS session window Type in ‘SET’ and press the Enter key. Look for the PATH= statement and determine whether the C:\Program Files\MQSeries Client\bin folder has been added to the path statement. If it has, verify that the folder actually exists on your system and contains approximately 40-45 files mostly DLLs. If not the install failed and will need to be uninstalled and reinstalled.. If the folder and it contents do exist but the path statement doesn’t reference it, you will need to either uninstall the MQSeries Client and reinstall it or you will need to add the path to the folder to the environmental variable Path= manually. To uninstall the MQSeries Client use the Control Panel Add/Remove Programs applet and remove any software in the list named similar to IBM MQSeries or IBM WebSphere MQ.

Submit MM via Web or Send MM Draft To fails or returns: DB2000 General Error 3265: Item not found in this collection. MMprint cmdSumitWeb, log on error. We have seen this error about a dozen times. It has always been caused by corruption of, or absence of certain registry settings normally created by the setup of the default browser. The Installation Log diagnostic can usually but not always diagnose this condition. The default browser must be able to handle HTTPS:// URLs. This in turn is controlled by HKLM\SOFTWARE\CLASSES\https registry settings. We have found that the easiest way to solve this problem is to follow the following procedure: Go to www.mozilla.com and download and install Firefox.  Use a standard setup as opposed to a custom setup. Start Firefox, and use the Tools Menu, Options, Main Tab to set and make sure that Firefox is now your default browser. Get out of Firefox. Start Internet Explorer. Use The Tools Menu, Internet Options, Programs Tab to set the checkbox that says Internet Explorer should check to see if it is the default browser. Once you have set this checkbox a button should appear asking whether Internet Explorer should be set as the default browser. Make it the default. Stop Internet Explorer. Start DB2000 and try again. It should now work. What this procedure does is to force Internet Explorer to rebuild some of its registry settings. In every instance so far, this procedure has corrected the problem.

Unable to add a member to a grid such as in the OD-2 or merit mark grids. Make sure that the member is not an affiliate. Make sure that the member is old enough. Check the Birthday field. If it's merit marks, remember that the commander can't be added. If it's merit marks and the correct commander can't be inserted as the submitting officer, check the SQ Rank field of the Roster grid to ensure that the current commander has the correct rank, and that no one else is also marked as commander.

Error 75 Path-DB2000 loosing track of path to database. Fixed in later versions.

Back to Table of Contents