----- Original Message ----- From: "gilbert9" <gilbert9@flash.net> To: <FAMILY-ORIGINS-USERS-L@rootsweb.com> Sent: Saturday, December 28, 2002 1:24 PM Subject: [FO] New Databases > 1. As I said in an earlier email, I had a computer crash, with the help of people from this list I got my "main" database restored. > > I'm now trying to restore some smaller secondary databases but I get the following error message: > > CODEBASE ERROR > error# -210 > error# 94003 > unrecognized field name > d4field number > SORTORDER > > I then click OK and get > error# -935 > error# 94001 > null input parameter unexpected > d4 field > > It then exists the program. Any help? > The program's author (Have a Happy New Year Bruce!!) is about the only one to really understand the errors cryptic message but in general the description is below: -210 Unrecognized Field Name A function, such as d4field, was called with a field name not present in the data file. What *YOU* should do is follow the author's recommendation at the homepage for Formalsoft's Family Origins: http://www.formalsoft.com/faq.htm "I just got a "CodeBase" error in Family Origins. What does it mean?" CodeBase is the database engine which Family Origins uses. If you get a CodeBase error, it means that something may be wrong with your data. Each CodeBase error will also have a negative number associated with it that tells what type of error occurred. If you receive CodeBase error -40, or -120, you probably don't have enough free disk space to do whatever function you were trying to do (like importing a GEDCOM file). Error -60 means Family Origins couldn't open one of your files. This could either be because the file doesn't exist, or because you are trying to open two copies of the database at the same time. Any other error most likely indicates a corruption in your database. If this occurs, try the following: 1.Delete the FOWIN.INI (or FOWIN32.INI if using the Win95 version) fil e from your WINDOWS subdirectory. 2.Delete the xxxP.CDX data file (where xxx is the name you gave your database). For example, if your database is named SMITH.FOW, delete the file named SMITHP.CDX. 3.Run Family Origins and open the database. This will rebuild all the indexes. Check if this fixes the CodeBase problem. 4.If you still have problems, try exporting the database to a GEDCOM file, then importing the GEDCOM file back into a new database. You may lose some information (like photo links), but it should clean up any problems with CodeBase errors. > 2. What is the simplist, easiest way to backup and then be able to restore (in case you lost your data) a database? > From the Family Origins Help file: To back up your data, 1. Choose Backup from the File menu to open the Backup Current Database dialog. 2. Click the radio button preceding your choice of backup files. Choose the Normal option to back up your files to a compressed .zip file, or choose Disk-spanning backup to back up your files in their original form (not compressed or zipped). Click OK to proceed with the backup, or click Cancel if you decide not to back up the files at this time. 3. Enter the path and file name for the backup file. (See Using file selector dialogs for information about choosing a file from a file selector dialog.) If you have backed up this information previously, the name of the file will appear in this dialog automatically. Click Save or OK to back up the files. The .ZIP extension is added automatically. What is a GEDCOM file? GEDCOM is an acronym for Genealogical Data Communication, and was developed as a standard for exchanging computerized genealogical data. Most genealogical software programs can import and export GEDCOM files. This makes it easy to exchange and share information with relatives and others. GEDCOM files also are used for submitting genealogical information to the Ancestral File data collection and TempleReady programs (LDS users). Maybe both you and your uncle are working on your family tree, and he wants to be able to add the information you have discovered into his database without entering it manually. If he uses a genealogy software program that imports files from a GEDCOM format, you can send him your information as a GEDCOM file, and he can import it into his genealogy program. To export a GEDCOM file, 1. With the database containing the information you want to export open, choose GEDCOM from the File menu and then choose Export GEDCOM from the submenu that opens. If you prefer, choose the Export GEDCOM button on the toolbar. 2. In the GEDCOM File to create dialog that opens, indicate the path and choose a file name for the new GEDCOM file. The extension .GED will be added automatically. Click Save or OK when the file name and path are correct. 3. Indicate whether you want to export the entire database or only select individuals by marking the radio button preceding the appropriate selection. See Selecting people to export for more information about selecting people to export. 4. Choose the destination of the GEDCOM file you are exporting by clicking the radio button preceding your choice. Ø General - To exchange data with other software programs or other people using Family Origins. Ø Ancestral File - To submit your information to the Ancestral File data collection. Ø TempleReady - To submit your information to the TempleReady program (LDS users). The destination you choose will affect the data format of the export file. 5. Mark the check boxes preceding your choices of the following export options: notes, sources, addresses, correspondence log, todo items, and multimedia links. If a box is marked, that action will occur. For example, if the box preceding Export sources is marked, the sources in your database that are attached to the people you have selected will export along with the individual information. If the box is left unmarked, the sources will not be included in the export file. 6. Check whether you want to preserve word wrapping in your notes. Usually you will want this checked, but some older programs do not support word wrapped notes when importing GEDCOM files. 7. Click OK to create the GEDCOM file. The extension .GED is added automatically to the file, and it is saved in the location you specified in step 2 above. If the GEDCOM file is too large to fit on a single floppy disk, you will be asked to insert another disk to continue the file on. Copyright © 1991-2001 FormalSoft, Inc. All rights reserved.