translation error

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

A file error has occurred in the Tab Separated Values(Windows) translator
while initializing a translator to build a field map.

why this is happenning?
 
You're asking for a possible cause without providing any kind of specific
information.

So questions for you are (and a request to anyone who poses such general
questions - please provide enough DETAILS on first post to save everyone
time and increase the chances of you getting a response at all. Am sure this
is a sentiment felt by all those who answer questions here in the newsgroup
or in any kind of support capacity for that matter.):

#1 - Outlook version?
#2 -What is the exact error message you rec'd?
#3 - Does this tab file contain a header row (first record contains the
field names for all subsequent records in the file)?
#4 - How did this file get constructed?
#5 - Can you open this file in Excel or import it via MS Access? (in short -
why do you think this is a valid file?)

Generic answer to probable causes?

#1 - You're tab file is not constructed properly or
#2 - The first record contains illegal characters in the first row (easily
caused if there is no header row) or
#3 - The first row contains less fields then the rest of the records or
#4 - Your Outlook import components are corrupted or
#5 - ??????????

One thing we know for sure is that Outlook has no problem importing properly
constructed tab delimited files but can be less then informative then one
would like when there are issues with the input data.

Karl
__________________________________________
Karl Timmermans - The Claxton Group
ContactGenie - Importer 1.3 / DataPorter 2.0
"Power contact importers for MS Outlook '2000/2003"
http://www.contactgenie.com
 
Outlook 2003 and problem was phone number format, it was more than 10 number
and wasn't liking it. It is fine now.
 
Thanks for responding but "phone fields" are free-form text fields in nature
and not restricted to being 10 digits - ergo the problem was related to
something other then the solution you described (not suggesting that you
didn't resolve it by reducing the phone numbers to 10 digits and this should
not to be interpretted as a challenge to your skills in any way - but
whatever you did, resolved another issue and # of digits wasn't it - unless
you uncovered another Outlook anomaly that we're not aware of and we
certainly have run across a few of those over the last couple of years).
Only responding/mentioning this for others who may read this and get misled
by the solution in your response.

Karl

PS - One of the reasons that I monitor this forum is to learn what problems
people are running into and make sure that we cover those issues in our own
products (both from an import and export point of view). To humor myself -
changed one of our test files to include all kinds of strange phone numbers
in a tab delim file including large digit numbers (and phone numbers with
different formats etc) and ran some internal tests. Using just the native
Outlook Import wizard - the import function worked exactly as expected so
the rethorical question is- what problem did you solve?

__________________________________________
Karl Timmermans - The Claxton Group
ContactGenie - Importer 1.3 / DataPorter 2.0
"Power contact importers for MS Outlook '2000/2003"
http://www.contactgenie.com
 
Back
Top