You aren't getting "incompatible versions" messages, right?

"Marco" <xo[at]libero.it> wrote in message
news:eTwKb.234108$e6.9257071[at]twister2.libero.it...
- quote -

For example I am not lucky!!!
I tried the salv.exe but it doesn't work on my data!
I was using an Italian Money 2000 file and I get the same error of Mark.
I'm trying to download the trial of 2004 and let's hope that it will work.
Any other suggestions???

Great. Thanks for the feedback. Consider yourself lucky. This hasn't worked
for all too many users.

"Mark" <anonymous[at]discussions.microsoft.com> wrote in message
news:066f01c3d3f4$7311c050$a101280a[at]phx.gbl...
- quote -

- quote -


Thanks again.

There will be a new Q/A in the FAQ on the web shortly:
---
Q): I thought Money files were supposed to be upward compatible. How come
Money[new] crashes when upgrading my Money[old] data file?
[Relevant to Money2003 (v.11) and up]

A): Most users find the file upgrade process painless. Beginning with M03, a
significant number of users don't. For these users, a range of outcomes from
Money just crashing to misleading error messages about the file being
read-only to missing data in the upgrade file result instead. The exact
reasons for this are unclear, but it would appear that the upgrade code has
become much less tolerant to "damaged" files. (Here a "damaged" file means a
file that has somehow become inconsistent with itself or not conforming to
the "normal" structure. Here "somehow" generally seems to be by Money
itself, though things like End Task when the CPU shows 100% use by Money and
the application is reported as not responding "just because" Money is slow
and non-responsive may also be factors.)

The workarounds identified include:

- Many users have found success by running the msmoney -s repair technique
on the original data file from the original version then upgrading the
repaired file. For people who have nothing left of the original version
besides a set of backup floppies, this is not an option.

- Using the salv.exe repair tool from the newer version or from Microsoft
Support on the data file before upgrading then upgrading the repaired file.
As above, this method does not work with .MBF files or with .MBF files
spread across multiple floppy disks.

(For more information of the repair tools and file corruption in general,
see "I think my file has been corrupted. How do I tell? What do I do then?")

- Some users have found/and or been advised by Microsoft Support that an
intermediate upgrade through, say, M02, first solved the problem. Of course,
finding a CD of M02 can be difficult.

- Some users have ended up resorting to QIF Export/Import to get the data
out of the old version and into the new version as a better choice than
losing all of their data completely. This is a last resort.

- Some files that could not upgrade in M03 can upgrade in M04.

Note that several of these methods do not apply if all you have is backup
floppies or files. This is one reason that we always recommend upgrading by
moving the entire original .MNY data file rather than going through the
backup/restore process.

Finally, note that it is probably a good idea to confirm your installation
of the new version of Money is good before going down any of these paths. To
do this, open the Sample data file located in the Program Files\Microsoft
Money directory or try to create a new file.

"Mark" <anonymous[at]discussions.microsoft.com> wrote in message
news:029f01c3d318$1dfb2520$a101280a[at]phx.gbl...
- quote -

When I try to import my Money 2000 file into Money 2003 I
get an error stating that it cannot open the file,
possibly because it is a read-only file or you do not
have permission to change it.

Has anyone else run into this?

I know the file works fine in Money 2000. Could it be to
large to import? It's ~18 Meg.

Thanks for your help.

Mark