T
Tom McNally
Company I work for often resorts to Excel as the medium for transferring
data as well as specialized reporting. The key identifier EmployeeID field
is a 5 character (varchar) numeric string (examp '84434') and sometimes a
mixed alphanumeric ('B3321') since we've run out of numbers and had to make
the switch.
In Access97 I could always manage to import these spreadsheets that had this
combo. But Office XP blows every time I try. I just ran into this
frustrating problem late yesterday and had to resort to an old machine with
'97 on it to at least import the data into a database/table and then open up
XP and import from there. Since we just converted over to Office XP, and
nearly all of the converted machines have '97 removed, this makes for one
heck of a mess if there is no "fix."
Have tried formatting the suspect cols in Excel as 'text' and
copying/pasting into new workbook; saving as older workbook type, all to no
avail. Even reinstalled Office XP. Many of the internal reporting systems
have an automated export to Excel feature to save data in this format, so
this key feature is heavily relied upon. Row counts, btw, are usually 2000
or less. Happens more often than not, so am wondering if it's just the
Excel import feature or some dll or other conflictin program that's creating
the problem. Am using XP Professional with latest service packs installed.
Also have VS Studio .NET
Any ideas what I can do?
data as well as specialized reporting. The key identifier EmployeeID field
is a 5 character (varchar) numeric string (examp '84434') and sometimes a
mixed alphanumeric ('B3321') since we've run out of numbers and had to make
the switch.
In Access97 I could always manage to import these spreadsheets that had this
combo. But Office XP blows every time I try. I just ran into this
frustrating problem late yesterday and had to resort to an old machine with
'97 on it to at least import the data into a database/table and then open up
XP and import from there. Since we just converted over to Office XP, and
nearly all of the converted machines have '97 removed, this makes for one
heck of a mess if there is no "fix."
Have tried formatting the suspect cols in Excel as 'text' and
copying/pasting into new workbook; saving as older workbook type, all to no
avail. Even reinstalled Office XP. Many of the internal reporting systems
have an automated export to Excel feature to save data in this format, so
this key feature is heavily relied upon. Row counts, btw, are usually 2000
or less. Happens more often than not, so am wondering if it's just the
Excel import feature or some dll or other conflictin program that's creating
the problem. Am using XP Professional with latest service packs installed.
Also have VS Studio .NET
Any ideas what I can do?