On line price updates corrupting number of shares

Recently there has been a signficant change in the way Money handles
updating investments with the latest prices.

Before Sepetember (and going back to at least 1997 when on-line updating
became available and I started using on-line updating) when you hit
"Internet Updates" only the LATEST price for a stock was downloaded.

Now suddenly a complete history of weekly prices is downloaded. This in
itself is not necessarily bad, but for a signficiant number of stocks in my
portfolio PHANTOM SHARE SPLITS have been introduced. ie share split when in
fact there were none.

eg Australian stock AMP now shows a share split of 103 for 100 on 21st May
2007. Where did this come from?

This obviously changes the number of shares for each asset where this has
occurred, essentially corrupting your portfolio.

People may not immediatley notice that this has happened. But when I checked
the number of shares for each asset I found that around 25% of then had
changed for absolutely no reason. I went back to backups and repeated the
process and the same thing happned.

I though that a glitch of this magnitude would have been fixed promptly. But
in the several weeks since I discovered the error nothing has been fixed.

I notice other posts on this newsgroup about this problem, but none for a
few weeks. A colleagueof mine also has exactly the same problem -- it's
certainly not a problem specific to my setup.

Deleting the share split does not fix the problem as the next time you
update prices it comes back. Changing the split to a 1 for 1 split does
restore the number of shares to the correct value and this prevents the
on-line updates from changing it, but this is unsatisfactory as, firstly, a
share split is now showing when there wasn't one (this is confusing and
incorrect) and seondly it's patch to fix a problem which just may pop up
somewhere else in the future.Who knows what stocks it will affect next week
or month. It's important to fix the problem, not to work around it.

Can somebody from Microsoft comment on this problem? It's a very serious
problem which compromises the integrity of what should be a reliable finance
package.