Standard(?) outlook import/export macro

[Alisdairjohnston]

I am using A13 on W8.1 alongside Outlook 2013. I am trying to build a project which will automate my home business. Like many, I use Outlook for my contact tracking. I want to be able to export and import contacts from my Database, and A13 provides 2 built-in Macros to do this.

Problem is, in my Database, they will only import or export the very basic contact information. (First NAme, Last Name, Firm etc). They will not import or export updated phone details or Remarks.

Yet when I try this in the MS-provided template (Desktop Time and Billing) it works seamlessly. Can anyone please suggest what I may be doing wrong?

Thanks in advance.

 

[Alisdairjohnston]

No takers? Surely someone must have come across a similar problem? Or is this a well-known glitch among the cognescenti?

 

[Alisdairjohnston]

OK, call me stupid. If over 150 people read this post, and can't be a**d to reply, to something which MUST be an integral problem with Access, why should I bother asking the question? Thanks and goodbye.

 

[spikepl]

A few things for you to consider:

1. This is a volunteer forum. Members provide advice when and if they feel like it. If you do not like the speed then pay someone.
2. Many more users just peruse the posts without adding anything themselves, so you can conclude absolutely nothing from the number of views.
3. You use w 8.1 and A2013 A vast majority does not use W8.1 and A3013 - the industry HATES being pushed into updates, and most of the pros are much more versed in the older versions.
4. You ou have some specific Outlook interfacing problem. This problem may simply not have been encountered by any of the users here, should it really be a new Access feature.
5. You are claming "integral problem with Access" despite the fact that "in the MS-provided template (Desktop Time and Billing) it works seamlessly". The fact thus does not support your claim. Also, error 40 is fairly common among those who blame Access, their computer or the position of the planets.
6. Getting miffed is utterly pointless. Bump you post occasionally, and also post on the other access fora, while maintaing the crossposting etiquette: http://www.excelguru.ca/content.php?184

 

[CJ_London]

I'm one of those not familiar with 2013 and don't use macros but common sense says to me that you could look at the template macro, compare with the access 2013 macro and make the changes - or copy the macro if that can be done.

 

[Alisdairjohnston]

Spike,

Thank you for your post. Firstly let me apologise for my churlishness in posting such an asinine comment - it is perhaps evidence of my frustration with my own lack of knowledge, and my inability to make such a potentially useful (to me) feature work. You are, of course, entirely correct in all of what you say - particularly with the point about the Template working. I'm not familiar with Error 40 - is that techspeak for operator blames machine?

I am not in the "the industry" and am merely trying to use Access to make my day job easier. However I do share your frustration with being forced into upgrades and losing support for older versions of Office. I think MS see Access as a bit of a poor relation.

Off to eat some humble pie - thanks for your tolerance.

A few things for you to consider:

1. This is a volunteer forum. Members provide advice when and if they feel like it. If you do not like the speed then pay someone.
2. Many more users just peruse the posts without adding anything themselves, so you can conclude absolutely nothing from the number of views.
3. You use w 8.1 and A2013 A vast majority does not use W8.1 and A3013 - the industry HATES being pushed into updates, and most of the pros are much more versed in the older versions.
4. You ou have some specific Outlook interfacing problem. This problem may simply not have been encountered by any of the users here, should it really be a new Access feature.
5. You are claming "integral problem with Access" despite the fact that "in the MS-provided template (Desktop Time and Billing) it works seamlessly". The fact thus does not support your claim. Also, error 40 is fairly common among those who blame Access, their computer or the position of the planets.
6. Getting miffed is utterly pointless. Bump you post occasionally, and also post on the other access fora, while maintaing the crossposting etiquette: