Unfortunately, no -- the data was discarded when the error occurred.
Apparently, the glitch must have caused BCM to interpret all the newer data
as records in the host db that had been removed on the next successful sync,
and then deleted it from the offline db.
Exporting is a good idea though, in case I encounter an error like this
again.
Thx.
"Luther" wrote:
> On Sep 27, 10:39 pm, BlueJay <Blue...@newsgroup.nospam> wrote:
> > I entered several hours worth of BCM data into my laptop, and then
> > reconnected to the BCM host machine. After more than an hour of just
> > watching the "sync" message sit on my screen, I clicked cancel to stop the
> > sync process so I could (finally) get back to working with Outlook. The
> > cancel button didn't seem to have any effect, so after another 20 minutes, I
> > finally did ctl-alt-del and stopped Outlook from the Program manager.
> >
> > When I restarted Outlook, it tried to sync again, but popped up an error
> > that it couldn't sync and that the object had already been deleted. I
> > restarted Outlook again, changed BCM to offline and then back online, and the
> > sync appeared to work. But when I went back to my folder, all my hours of
> > work were missing?
> >
> > I assume all that data is a lost cause, and there's no way to get it back.
> > I'm still in disbelief that all that work is gone... I'm so completely
> > disappointed, beginning to wonder if I made the right choice to invest in BCM?
> >
> > The only thing I can think of is that I'm syncing over a wireless network --
> > could that have impacted anything? I think I might have lost network
> > connectivity briefly just after the sync started. Do I dare try to re-enter
> > the data again offline?
> >
> > Anyone have any ideas for what I can do?
> >
> > Thanks!
> > BlueJay
>
> Is the unsynced data still in your offline database? If so, you could
> try exporting it to a BCM file, then connecting to your shared
> database and importing that file. All the records that are more recent
> in the BCM file should be updated in the shared database.
>
>
|