 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWordDirectoryUser Groups Related Topics Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ... |
MS Office Forum / Outlook / Contacts / November 2007when importing outlook contacts how can the STMP addition be ommi
When I copy contacts from Outlook on my workstation in CVS format and import these copied contacts onto Outlook on my notebook in the process of copying STMP lines /additions with names are automatically added, rendering the whole contact database useless until these STMP additions are manually deleted again. What can I do i.e. setting filters and if so which filters in the copying process? Any constructive suggestion is very much appreciated. Thank you Why would you use a foreign file format and import to transfer Outlook data? Why would you not use an Outlook data file?  SignatureRuss Valentine [MVP-Outlook] > When I copy contacts from Outlook on my workstation in CVS format and > import [quoted text clipped - 7 lines] > Thank > you I will have to find out, whether it works. Would have thought that Excel or CVS are commonly used and schould universally do the trick. The question though is, why and where are these STMP additions created and why? Will come back with results a.s.a.p. Kristian > When I copy contacts from Outlook on my workstation in CVS format and import > these copied contacts onto Outlook on my notebook in the process of copying [quoted text clipped - 3 lines] > copying process? Any constructive suggestion is very much appreciated. Thank > you No answer is possible without knowing what your data source was and how you mapped your fields. No one should ever transfer Outlook data by exporting and importing through a different format unless they want to lose or alter that data, as you are illustrating. You should only use Outlook's native data file format to transfer data, but again without using export and import. Just copy the data file and open it in the other installation. SignatureRuss Valentine [MVP-Outlook] >I will have to find out, whether it works. Would have thought that Excel or > CVS are commonly used and schould universally do the trick. The question [quoted text clipped - 13 lines] >> Thank >> you Russ, will let you know. Tx k > No answer is possible without knowing what your data source was and how you > mapped your fields. [quoted text clipped - 21 lines] > >> Thank > >> you Russ, It worked in PST format. Thank you very much Kristian > No answer is possible without knowing what your data source was and how you > mapped your fields. [quoted text clipped - 21 lines] > >> Thank > >> you Excellent. Thanks for posting back. SignatureRuss Valentine [MVP-Outlook] > Russ, > It worked in PST format. [quoted text clipped - 36 lines] >> >> Thank >> >> you Sorry Russ to bother you again... In practical use I now noted it doesn't work: 1) A seperate Contacts Folder was created in Outlook (Identical thought to the original from my Office workstation). 2) After having moved the contacts into the original Contact folder it seemed to be o.k. but wasn't: If you try to create an Outlook Distribution list, and you want to add members it tell theat there are no addresses in the contact list, despite there are nearly 1,500...?? Question: have I done something wrong, or is there something wron with Outlook?? Can you put your finger on this one? Looking forward to hearing from you in due course regards Kristian p.s. I still don't understand as to why MS offers the option of importing and exporting, if one cant use it due to the objections you had and as to why and where in the im/exporting process data is added, that doesn't belong there? > Excellent. Thanks for posting back. > > Russ, [quoted text clipped - 37 lines] > >> >> Thank > >> >> you What was the original source of these DL's? Were they created in the Active Directory? No one knows why the option to import and export Outlook data still exists. It did work back in Outlook 97, but it hasn't worked for so long now that it should have been removed long ago. I suspect it is with many other things in Outlook. Removing a dysfunctional feature takes more work than just leaving it in, so they just leave it in. Pretty sloppy if you ask me, but they don't. SignatureRuss Valentine [MVP-Outlook] > Sorry Russ to bother you again... In practical use I now noted it doesn't > work: [quoted text clipped - 66 lines] >> >> >> Thank >> >> >> you Sorry for answering late. Was sick. If DL means data source, then yes, the attresses/contacts where created in Outlook. All I need to do is to put a duplicate of the contacts every week onto my note book in order to have a replica. If you have any other idea i.e. other than ex - and importing I would a happy bunny. Kristian > What was the original source of these DL's? Were they created in the Active > Directory? [quoted text clipped - 75 lines] > >> >> >> Thank > >> >> >> you No. DL = Distribution List. DL's were the subject of your last question. I'll guess that your actual problem isn't with DL's, however, but the fact that the Contacts you are transferring aren't behaving as expected. Is that the real question? If so, troubleshooting that problem would require knowing: 1. How and where the original Contact data was created (including whether you are using a local data store or an Exchange mailbox) 2. How exactly you transferred the Contact data to your notebook, in complete detail. SignatureRuss Valentine [MVP-Outlook] > Sorry for answering late. Was sick. If DL means data source, then yes, the > attresses/contacts where created in Outlook. All I need to do is to put a [quoted text clipped - 100 lines] >> >> >> >> Thank >> >> >> >> you Russ,Tx for the prompt reply:The DL or Contact database was purely and only created in Outlook. The exporting purely and only done in the Outlook environment, which may be dodgy by now. Having had a look at other problems of other dicussion group members I seem to be in the very best company as quite a lot of similar problems seem to exist...Wouldn't it be a good idea, if MS could look into such an obvious problems? Karl Timmerman suggested to copy the original pst file. sounds logical. I hope it works. Kristian > No. DL = Distribution List. DL's were the subject of your last question. > I'll guess that your actual problem isn't with DL's, however, but the fact [quoted text clipped - 109 lines] > >> >> >> >> Thank > >> >> >> >> you Karl and I are suggesting the same thing (and always do). But you keep leaving out the relevant details that permit a specific set of instructions for your situation. Neither of us even knows if you are even using a PST file as your data source or some other data store such as an Exchange mailbox. At any rate, many of us post information on how to transfer Outlook data correctly here on an almost daily basis. Feel free to read those references. http://www.slipstick.com/config/backup.htm http://www.howto-outlook.com/Howto/backupandrestore.htm http://office.microsoft.com/en-us/assistance/HA010771141033.aspx SignatureRuss Valentine [MVP-Outlook] > Russ,Tx for the prompt reply:The DL or Contact database was purely and > only [quoted text clipped - 144 lines] >> >> >> >> >> Thank >> >> >> >> >> you > The exporting purely and only done in the Outlook environment, This, I think, is the main source of your troubles. You never import and export to transfer data between Outlooks and Distribution Lists are one of the objects that suffer the most from that process. SignatureBrian Tillman [MVP-Outlook] #1) If the objective is to get your contacts from one machine to another and you have access to the source PST file, simply copy your PST file to the target machine, open the PST file on the 2nd machine and copy whatever info you need from one folder to another (make sure to take off the read-only attribute after you've copied the PST file to the 2nd machine if necessary). Import/export is definitely not recommended for purely moving native Outlook info between two machines regardless of data format used. As for the original SMTP question, all depends whether or not you actually mapped the email TYPE when importing especially if the email addresses being imported are not of the SMTP type (name@domain.com). #2) As for PST2PST importing/exporting - that can, in and of itself, lead to either (or both) immediate and/or future issues and in my opinion should be avoided at all costs unless there is some real pressing need/purpose (which is something I've yet to encounter under normal circumstances). This is especially true if the contact info has been upgraded over multiple versions of Outlook over the years. The creation of a new folder when doing PST2PST import/export is the way that process works. Karl ___________________________________________________ Karl Timmermans - The Claxton Group ContactGenie - Importer 1.3 / DataPorter 2.0 / Exporter "Power contact importers/exporters for MS Outlook '2000/2007" http://www.contactgenie.com > Sorry Russ to bother you again... In practical use I now noted it doesn't > work: [quoted text clipped - 66 lines] >> >> >> Thank >> >> >> you Thanks Karl, I'll try this one next. As regards to STMP mapping. Is there a kind of switch/ setting one could perhaps change temporarily. British Telecom/ Yahoo as our ISP provider have set all our computers to STMP. I would guess a method should exist to switch, as effects only the outgoing mail. Sorry for the late reply: I was rather sick in between. Looking forward to hearing from you Kristian > #1) If the objective is to get your contacts from one machine to another and > you have access to the source PST file, simply copy your PST file to the [quoted text clipped - 92 lines] > >> >> >> Thank > >> >> >> you Hi Karl, I finally made it : One important thing though to remember: After copying the files one has to look at the property of the contact list and tick the little box in properties in order to make it and addressbook list - otherwise , for instance when setting up a distribution list, no adresses are present in the dialogue box. As for the other comments: i HAVE allways OPERATED IN THE oUTLOOK ENVIRONMENT, HENCE MY DESPARATION. That is and remains a point MS should -in the interest of the users - look at. Tx again Kristian > #1) If the objective is to get your contacts from one machine to another and > you have access to the source PST file, simply copy your PST file to the [quoted text clipped - 92 lines] > >> >> >> Thank > >> >> >> you I conclude then after all said and done - all things are finally working for you, which is a good thing (all that matters really). As for Outlook's "anomalies" and "undocumented features (to use a polite description)", I believe that someone took the phrase "no pain, no gain" to heart when it comes to enabling anyone to master the best ways to deal with Outlook data, its containers, and modes of operation :-) (we can attest to that first hand once one strays outside the norm even for the simplest and most basic of things). I suspect the cause of that being purely to make things backwards compatible (or likely the better word being "useable") as much as possible particularly when it involves data from multi-generations of Outlook. Karl ___________________________________________________ Karl Timmermans - The Claxton Group ContactGenie - Importer 1.3 / DataPorter 2.0 / Exporter "Power contact importers/exporters for MS Outlook '2000/2007" http://www.contactgenie.com > Hi Karl, I finally made it : One important thing though to remember: > After copying the files one has to look at the property of the contact [quoted text clipped - 128 lines] >> >> >> >> Thank >> >> >> >> you |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.