I ran into this exact problem and I may not have a clear answer for you, but
maybe some things to consider. I have been using money since the 95
version, upgrading every year, and I use it to its full extent. Around 1999
I went to open the file one day and it was suddenly corrupt for no apparent
reason! After hours of narrowing down the issue, I determined that there
was a point where it would work fine but if I added one more record (in any
account) it would corrupt the file. I am a VB/ASP/ASPX/.NET/SQL2000
programmer and after discussing this with the forum at the time, concluded
that there was only so much data the file could handle. I started archiving
a year every January. When 2003 came out, I thought innovations in the
technology would have overcome this issue, but when I let my annual archive
go undone, I received a corruption error in late February. I was ready with
backups, brought the file back, archived and continued and I am still having
no issues. I am currently running 2003.

So, I don't know what to make of this. I can tell you that I absolutely
LOVE the program and find it intuitive and easy to use (moreso than its
competition), but over the past 7 years I have found critical flaws with the
program that are absolute pains to deal with and one that I am dealing with
right now that does not seem to even have a work-around. IMO: MSM is not
as well-developed as it should be for the number of years in production.
Don't get me wrong... I love MS, but the fact is that (at least in this
case), they seem to release on marketing and cosmetics and not on true
feature and performance improvements. My opinion of course.

My suggestion: there is a utility you can find in the KB that will attempt
to repair the file. I've never had any luck with it, but maybe it will work
for you. If that doesn't work, get the best backup you can, archive a year
off the front, bring the file up to date and create a task for yourself to
archive a year off once a year.

Best of luck to you!

Schoo


----- Original Message -----
From: "ARosenthal" <anonymous[at]discussions.microsoft.comNewsgroups: microsoft.public.money
Sent: Wednesday, June 23, 2004 1:18 PM
Subject: Huge *.mny file


- quote -

"ARosenthal" <anonymous[at]discussions.microsoft.com> wrote in message
news:2083901c4594e$7b9d3d00$a101280a[at]phx.gbl...
- quote -

- quote -

options and look.

It's probably MSISAM, not Jet4--exactly what the difference is seem likely
to be semantic. 20MB is not huge. Mine's 50MB.

<anonymous[at]discussions.microsoft.com> wrote in message
news:2053701c45950$c75e7a90$a301280a[at]phx.gbl...
- quote -

If you are using beta 2005, then you need to refer this to the appropriate
beta newsgroup.

--
Glyn Simpson, Microsoft MVP - Money

Check http://support.microsoft.com/default...d=fh;EN-GB;mny
for UK tips and fixes for MS Money. To send Microsoft your wishes or
suggestions, use http://register.microsoft.com/mswish/suggestion.asp
or email mnyukwsh[at]microsoft.com especially if it's a UK specific wish.

I do not respond to any unsolicited email regarding Money

<anonymous[at]discussions.microsoft.com> wrote in message
news:2053701c45950$c75e7a90$a301280a[at]phx.gbl...
- quote -

Since this is Jet4 db, the sizing yields a large
probability to corruption. I am using beta mny2005 and
thought it was MSDE by now, but saw no named instance
over there to indicate that ...

It is 20MB long ...

--A

- quote -

How huge is huge?

As to what you are doing wrong, I'd nominate worrying about the size of the
file and assuming a strong correlation between file size and performance.
See http://umpmfaq.info/faqdb.php?q=7.

"ARosenthal" <anonymous[at]discussions.microsoft.com> wrote in message
news:2083901c4594e$7b9d3d00$a101280a[at]phx.gbl...
- quote -

Greetings again
It happens that after several girations of money (99
onwards) I was left with a huge *.mny file. That is OK
since it carries my history around. However, it is taking
too long to load, so I wanted to archive old items. That
ended up with a corrupted .mny file and a useless
archive. What is that I am doing wrong?

--ARosenthal
MCS Dallas