Frequently Asked Questions for DOS applications:

Q: I am receiving an error message "Internal Error 1010"

A: This is usually indication of a corrupted index. If you can enter the system, go to File Utilities, then select Index Files, then press the F8 key to Tag All.  Then press the Enter key to begin reindexing.  If you can not enter the system because of this error.  Go to the directory where the program resides and enter the following DOS command:  DEL *.NSX   then run the program.   You should see a progress bar indicating the progress for reindexing.  Once this is done, you should be able to proceed

Sometimes this error will occur because of a corrupted memo file.  If this is the case, you will need to restore the corrupted file from your most recent backup.  The file extension for the memo file is .SMT.  So, if the ORDHEAD.DBF file appears to be the one indicating the 1010 error, then you will need to restore the ORDHEAD.SMT file from you backup.  Reindexing as listed above would be a good idea too, to make sure that everything is working properly.

 

Q: I have received what appears to be a General Protection Fault error.  It is followed by a screen full of numbers and letters.

A: This is usually indication of a corrupted index. If you can enter the system, go to File Utilities, then select Index Files, then press the F8 key to Tag All.  Then press the Enter key to begin reindexing.  If you can not enter the system because of this error.  Go to the directory where the program resides and enter the following DOS command:  DEL *.NSX   then run the program.   You should see a progress bar indicating the progress for reindexing.  Once this is done, you should be able to proceed

 

Q: I run my application through Windows, and when entering a module, it simply dumps me back into Windows.

A: You may be receiving an internal error, but because you have the "Close on exit" check box checked for the application.  To check this, right-click on the Icon you use to run the application.  Choose properties.   Click on the Program Tab.  If the "Close on exit" check box is checked, uncheck it and run the application again.  At the place where it would exit back into Windows, look carefully for an error message.  It may be hard to see as the screen usually doesn't clearn.  If it is an internal error, see the FAQ entry on "Internal Error 1010".  Once this problem has been resolved, you can change the setting for "Close on exit" back to it's original setting.

 

Q: When reindexing I get an error "DOS File limit exceeded"

A: Check your config.sys (EDIT C:\CONFIG.SYS) to make sure that the files are set properly for your application.  If you do not know what the files setting for your system is, either check the manual or SupportBack2You@msdlg.com us for the information.  Once this has been updated, enter the program and it should continue reindexing where it left off.

 

Q: When I run a Grumpfish query, and print my report, not all of the fields show up.

A: When you press F7 to print, then select Printer, go into the Default Settings and increase the Page Width. Setting it to 250 will usually do the trick.

 

Q: When I try to run a Grumpfish Query, I am told "unable to find file" (filename will be stated)

A: If the query was created on a different drive or directory, this information is saved in the .QRY file itself. To fix this, load the .QRY file into a DOS Text Editor (DOS Edit, or Windows NotePad) and change any file path found at the top of the file. Save the file and this should solve the problem. You might want to make a backup of the file before you do this, in case something goes wrong while you are editing.

Q: My program is running extremely slow.

A:  There are several things that can cause this, especially if you are operating on a Network.  Here are some things to check.

  1. If you are running a Windows NT Server, make sure that the screen saver is turned off.  This uses excess CPU cycles and can cause a major slow down.
  2. If you are running a 10 Mega Bits Per Second network, you might want to consider upgrading to a 100 MBPS system.
  3. You may want to try to determine if the slow down is on the local workstation or the server.  The best way to do this is to install the application on the local workstation and run it.  If it runs fast, then the problem is with the network.