"Speed-dial Broken But Repaired" Error

[dcbehan]

Every time I go to use Speed-dial, I get the message 'Speed-dial was broken and has been repaired.' Once I hit OK, it dials the number fine. Whenever I look at my speed-dial list, it appears fine. Anyone else have this happen? Any solution you found. It's not that big of a deal but the purpose of speed-dial is speed, not navigating messageboxes.

Any help would be appreciated.

db

[iggy]

Every time I go to use Speed-dial, I get the message 'Speed-dial was broken and has been repaired.' Once I hit OK, it dials the number fine. Whenever I look at my speed-dial list, it appears fine. Anyone else have this happen? Any solution you found. It's not that big of a deal but the purpose of speed-dial is speed, not navigating messageboxes.

Any help would be appreciated.

db

Same error here. Anyone have a solution.

[k_kirk]

Not a solution but a question/hint towards collobrative discovery...

Are you backing up & restoring your XDA or databases etc?

Normally I do not get this message on a regular basis. I use SpriteBackup to backup the database file called speed.db. This database contains the speed dial entries. Each time I restore this database I get the error you mention.

It appears that the speed dial list is simply a list of references to Contacts database positions. Somehow the system must be tracking whether either of the two databases have been "touched" and then put it into the recovery mode mentioned. I guess the trick is to detect this change and counter it if needed.

Just pure speculation so please forgive me this is all rubbish and useless information.

[iggy]

Not a solution but a question/hint towards collobrative discovery...

Are you backing up & restoring your XDA or databases etc?

Normally I do not get this message on a regular basis. I use SpriteBackup to backup the database file called speed.db. This database contains the speed dial entries. Each time I restore this database I get the error you mention.

It appears that the speed dial list is simply a list of references to Contacts database positions. Somehow the system must be tracking whether either of the two databases have been "touched" and then put it into the recovery mode mentioned. I guess the trick is to detect this change and counter it if needed.

Just pure speculation so please forgive me this is all rubbish and useless information.

Interesting speculation K_Kirk, I backup using Sprite Clone and ActiveSync backup\restore function every few days. Maybe their is a connection.

[dcbehan]

I use Backup Manager daily for backup but have not restored recently. What I did do that seems to work is delete all the speeddials and redo them (as I only had three it was no big deal). Since I did that, I haven't had any problem.

The restore question indeed may be on the right track thought I'm not sure what you'd do about it other than start again.

db

[griffog]

I don't use Sprite nor do I backup via AS and I get the error regularly.

[belial]

The speed dial database is indeed a collection of OID links to the contacts database.

restoring your databases, by any means (except raw mode in sprite clone), causes the OID's of database records to change, breaking this link.

Sprite Backup repairs the link on restore, however, when you next synchronise with Active Sync, a full resync is performed because of the OID changes, and Active Sync does not patch the SpeedDial database appropriately.

if the OID link appears invalid on use, in 2003, it matches them up via name ot the contacts database, hense the "broken but fixed" message.

chuck@spritesoftware.com can send you a speedmatch.exe that does this to all speed dial links, perhaps if it can be made to run automatically after any active sync activity then you'll never see that message again.

You don't NEED to backup and restore to see this message however, Activesync quite commonly deletes and re-creates altered contacts, breaking any speeddial links to them.

..belial..