|
Just a very small point: The culprit is not the Axim or Dell, but Microsoft. When you re-established the partnership after the hard reset, I would bet you had given the "new" Axim the same device name it had before. When you sync'ed, what Activesync saw was the same machine attaching, but now with all appointments, contacts, etc., deleted. So Activesync did what it does, it synced the PC version to match what it assumed you had done on the PPC, erasing the entries.
Had you given the Axim a different device name, then synced, Activesync would have done just the opposite. It would have brought the NEW PPC into agreement with the desktop, downloading all contacts, appointments, etc. And if you call M$ about the "problem" they will say it's a "feature" and not be terribly sympathetic.
There is another way, and that is to have the PC always overwrite the PPC, at least for that first sync, then return it to reporting conflicts, but I have found that that does not always put ALL information back on the PPC, even though it should. I use the changed name approach now, and it works the way I want.
I know this doesn't help your immediate situation, but I've done that same thing myself. Fortunately I had a fairly recent backup of Outlook, so I was able to restore MOST of what I lost. It's also unfortunate that the documentation from M$ is a little less than totally clear on this point, but if you dig through the stuff at www.microsoft.com, you can find it. I think personally that Activesync ought to treat "major" changes the same way Windows treats "delete files" commands and get a confirmation that that is what I want to do. But I'm not Bill Gates, so I can't make it rational. (Nor can he, apparently ;) )
|