----- Original Message ----- From: "Margaret McEuen" <MargMcEuen@prodigy.net> To: <FAMILY-ORIGINS-USERS-L@rootsweb.com> Sent: Saturday, January 11, 2003 10:38 PM Subject: [FO] File extensions & sudden gigantic files > Hello everyone, > I just recently rejoined the list for FO and hope someone can help. > > I have had FO for many versions and now have FO 10. I have never had a > really big problem until now. I have had some files expand greatly when > I have been using the drag & drop feature between databases. > > In Nov. the back-up for my main file was 8,214 KB. Last week the same > back-up was 29,434 KB and I hadn't added that much! All of a sudden FO > is taking up most of the space on my disc partition of 1123MG. > > What does the .FPT extension mean? I think .CDX is index files and .DBF > is database files, but neither my husband, who is a programmer or I, who > am not, can figure out .FPT in this case.. The .FPT file has gone up to > 1,739,054 KB and all I have done is add a few names and drag & drop 5-8 > other names. The drag & drops now take forever too. At least 15 min. > for a few names that are copied. I only have it merge a person and copy > their descendants. I am sure to only mark those certain people to copy, > and no others. The copy box shows the correct number, but takes forever > to put them into the other file. > > When I checked the main file for record #s, it has 5994 ind., 2535 > families, 10663 events, 745 sources, 9860 citations, 2062 places, 70 > repositories, 72 to do, 24 addresses AND 3,562,711 multimedia ITEMS!! I > only have 132 pictures in various scrapbooks, not over a million items!!! > > I hope some of you can give me some ideas on what to do about this wild > expansion of FO and what might be causing it. It seems to have gone > berserk. > > Thanks for any help with this problem. > > Marg McEuen > NOTE: I am not a programmer, but my "general" understanding of those file extensions would be as follows: .DBF is the table file structure [stores data that *defines* the file's records consisting of different "fields" and their "sizes" (eg. SURNAME - "type" text - 32 characters maximum "size") -and- contains the contents of *most* of those "fields" of data] .FPT is the table memo file structure [stores "blocks" of data (that exceed a field's defined size), pointers to their location, -and- pointers to the next available "free" space (eg. General, Family & Individual NOTES - "type" text - "blocks" of 2048 characters maximum "size")] .CDX is the compound index for one (or both) of those structures that keeps "track of" (via pointers) each "field" (by name) -and- the actual "contents" of each field. When an operation to sort or gather, etc. is initiated by you, the user, rather than have to move the data, itself, all around (and take much longer)... these pointers are simply rearranged for "sorts" or referenced for "gathers", etc. .FOW is the control file for each FO database that handles the "housekeeping" for sake of a better term. Now, as to your problem. It would seem that you and your husband have done a good "detective's job" in spotting the anomalies. I can tell you , from personal experience, that I once had a "similar" problem. Here's the "scenario" that happened in my case: I wanted to "experiment" with one of my databases, so I quickly copied the 35 files that make up the database to a safe, temporary folder (I had already backed up my database before this). Then I "experimented" and when finished... I dragged & dropped the "originals" from the safe, temporary folder back to overwrite all their counterparts (or so I thought). But, what I had inadvertently done is "missed" one (when highlighting the "safe" files) and consequently not all 35 "original" files made their way back. This left a file from my experiment (probably a .CDX file) that had different pointers than should be. My database opened fine and I "unknowingly" packed my database, then backed up again to my alternate place upon exit. The next program that I went to run, immediately caused Windows to pop up a warning that I was getting "low on disk space" and like you, I discovered a huge change in file size for one of my .FPT files. Fortunately for me, I keep several iterations of backups and was able to restore my most recent with no loss of data. What I believe has happened is that the internal pointers between the records and the memo file have become corrupted. If one of these pointers *does* get corrupted, it usually points to a place *beyond* the "actual" end of your memo file and a subsequent "Pack Database" command causes your .FPT file to "grow" in size (although no additional data has been added). If this is the case, I don't *believe* it is "easy" to fix the existing files. If you do have recent backups, that is the way to go (just let the restore "overwrite" the questionable files. But, since you do not mention any FO errors and are inquiring to the list, it may be that you cannot do that without losing much work? Also, your mention of the *extraordinary* difference in Multimedia items counted, should warrant your looking at the Multimedia List under Reports--> Lists for anything unusual. The most likely alternative is to export a GEDCOM, then create a new database and import that same GEDCOM. Compare the file sizes after this operation and perhaps all will be "well and good" except for the loss of custom fact "sentence wording". Others on this list are more knowledgeable and can suggest other possible solutions. Email the list with any developments or further determinations and this list will rise up to attempt to help, of that I am sure! -=Kevin Benson=-