I searched the forum for syncing A5 data with Outlook and or pda phones--found a few posts that looked somewhat promising but no "Aha, success at last and here's how."
"Syncing" can mean several different things, so I'll get more specific: I have a client with a Verizon XV6800 cell phone which I gather uses the Windows Mobile 6 Professional OS. All he wants is for there to be an easy way for the contact data in his phone to reflect what is in an A5 table and for the phone data to be updated at least on a daily basis. So, for example, if a new contact record is entered in the A5 table, selected fields would be used to create a new "record" in the phone's BD, presumably when he does whatever with his phone that initiates an update. And if a contact's phone number in the phone DB was different (due to a change in the A5 table), then that A5 based number would be updated to the phone data at least on a daily basis. The updating would never go in the reverse direction, from the phone to the A5 table.
Since on his PC he uses Outlook, and since I have some reason to believe there is an easy way to "sync" phone data with Outlook data, one thought was to go from A5 to Outlook and then to the phone. Similarly, I have some reason to believe there is an easy way to go from an Access DB to Outlook, so how about an A5 active link to an Access table and then to Outlook and then to the phone? Or is there a far more straightforward way to do all of this?
I should add that even if there is a way to directly from an A5 table to the phone (bypassing Outlook), this client would still like an update from A5 to Outlook for other purposes.
Anyone have any experience, insight or whatever on any of this?
Ray Lyons
"Syncing" can mean several different things, so I'll get more specific: I have a client with a Verizon XV6800 cell phone which I gather uses the Windows Mobile 6 Professional OS. All he wants is for there to be an easy way for the contact data in his phone to reflect what is in an A5 table and for the phone data to be updated at least on a daily basis. So, for example, if a new contact record is entered in the A5 table, selected fields would be used to create a new "record" in the phone's BD, presumably when he does whatever with his phone that initiates an update. And if a contact's phone number in the phone DB was different (due to a change in the A5 table), then that A5 based number would be updated to the phone data at least on a daily basis. The updating would never go in the reverse direction, from the phone to the A5 table.
Since on his PC he uses Outlook, and since I have some reason to believe there is an easy way to "sync" phone data with Outlook data, one thought was to go from A5 to Outlook and then to the phone. Similarly, I have some reason to believe there is an easy way to go from an Access DB to Outlook, so how about an A5 active link to an Access table and then to Outlook and then to the phone? Or is there a far more straightforward way to do all of this?
I should add that even if there is a way to directly from an A5 table to the phone (bypassing Outlook), this client would still like an update from A5 to Outlook for other purposes.
Anyone have any experience, insight or whatever on any of this?
Ray Lyons
Comment