|
#2
| |||
| |||
| I guess my message--and I didn't make it clear--is that I'd use the "large" file (and keep a fallback path in case a problem crops up) and expect time, and an auto-compact cycle, to make the problem go away. I wouldn't view the size as a singular indicator of any problem. These Jet databases are funny things. My "Project Dinero" (homebrew playing around with Money replacement database) grows to almost 25MB when I run the routines that auto-populate it and do all of the merging and joining necessary to get the data in from the Money generated .CSVs. If I compact it, it shrinks right back down to about 10MB. "Art McClinton" <art[at]nova.org> wrote in message news:47GJf.395819$0l5.318552[at]dukeread06... - quote - > Yes disk space is cheap and I do keep older versions. I was wondering if > it did anything as the log did not indicate any errors corrected. Hence I > was considering not even using the new file. |
|
#1
| |||
| |||
| Thanks Dick. Yes disk space is cheap and I do keep older versions. I was wondering if it did anything as the log did not indicate any errors corrected. Hence I was considering not even using the new file. Dick Watson wrote: - quote - > 1) always keep copies of your data file from benchmark points--like before > doing stuff like this. > 2) If you use the file for a while it will probably auto-compact down to a > size much closer to your previous size. > "Art McClinton" <art[at]nova.org> wrote in message > news:kOxJf.395683$0l5.225304[at]dukeread06... > > I have had some occasional strange activity (During an Update while I was > > doing nothing I would occasionally get a pop up saying that I could not do > > what I was doing while the update was in progress) so I decided that I > > would like to run a salvage to see if any errors occurred within the file. > > Thus I started a normal repair of my 29MB data file. After a few minutes > > it finished and suggested I look at the log. The log showed that no broken > > records were found. Based on no errors I expected that the output file > > would be identical to the input file. However the resultant output file is > > 50NM in size. Any comments on what might be occurring would be > > appreciated. At this point I have not tried the 50MB file but do not find > > any reason to doubt the smaller files correctness. > > > Art |
| | |||
| |||
| 1) always keep copies of your data file from benchmark points--like before doing stuff like this. 2) If you use the file for a while it will probably auto-compact down to a size much closer to your previous size. "Art McClinton" <art[at]nova.org> wrote in message news:kOxJf.395683$0l5.225304[at]dukeread06... - quote - > I have had some occasional strange activity (During an Update while I was > doing nothing I would occasionally get a pop up saying that I could not do > what I was doing while the update was in progress) so I decided that I > would like to run a salvage to see if any errors occurred within the file. > Thus I started a normal repair of my 29MB data file. After a few minutes > it finished and suggested I look at the log. The log showed that no broken > records were found. Based on no errors I expected that the output file > would be identical to the input file. However the resultant output file is > 50NM in size. Any comments on what might be occurring would be > appreciated. At this point I have not tried the 50MB file but do not find > any reason to doubt the smaller files correctness. > Art |
|
#-1
| |||
| |||
| I have had some occasional strange activity (During an Update while I was doing nothing I would occasionally get a pop up saying that I could not do what I was doing while the update was in progress) so I decided that I would like to run a salvage to see if any errors occurred within the file. Thus I started a normal repair of my 29MB data file. After a few minutes it finished and suggested I look at the log. The log showed that no broken records were found. Based on no errors I expected that the output file would be identical to the input file. However the resultant output file is 50NM in size. Any comments on what might be occurring would be appreciated. At this point I have not tried the 50MB file but do not find any reason to doubt the smaller files correctness. Art |
| Tags |
| data, double, file, money, repair, size |
Similar Threads | ||||
| Thread | Forum | Replies | Last Post | |
| Money 2006 and size of Data File Daryle: My Money 2004 file is 32 MB. When I had problems with upgrading to M2005, support suggested that my file was too large to upgrade successfully. ... | Microsoft Money | 2 | 07-13-2005 07:27 PM | |
| Corrupt data file - repair does not help. Now what? Moshe Rosenberg: I have a similar issue like "Don Alwalt" had in this thread: ... | Microsoft Money | 6 | 06-09-2005 04:32 AM | |
| Any way to repair a corrupted money file? DRUAngell: I always keep a backup of my money file (exact copy) on an external hard drive. Recently, I've just done a clean install of XP on my machine and I... | Microsoft Money | 5 | 04-22-2005 01:59 PM | |
| Repair Corrupt File Bobbee: While Money 2004 has a simple click to reapir corrupt files, Money 2003 does not. My mom's bank account is showing trillions of dollars (I wish).... | Microsoft Money | 6 | 08-26-2004 01:42 PM | |
| Is there a way to repair a money 2003 file Brian W: I am having some minor but somewhat annoying issues with my Money file, and I was just wondering if there is a way in Money 2003 to repair the file... | Microsoft Money | 1 | 08-03-2004 04:23 PM | |
| Thread Tools | |
| Display Modes | |
| |