software

Windows 2002 SP2, Office 2003 SP2

I am trying to avoid potential problems with a new process and would
appreciate your input.

Right now we have a vast amount of data downloaded into over 200 Excel
files, into a formatted style (no database-style lists - the output looks
like a finished report). We refresh the data every month. We then have
another template file with a macro that opens up each of these data files,
imports selected sheets of data, does a save as, and moves to the next data
file. We have several different computers simultaneously running different
templates through this process each month.

My data supplier tells me that they can speed up my data download time
(which is currently about 2 weeks across 5 PCs) if they can put the data into
a CSV file instead of straight into Excel.

I see a lot postings about problems converting from CSV to Excel...is there
anything I can do to avoid problems? Anything I need to ask my supplier?
What types of problems are typical? Should I just not even consider the idea?

Thanks for your insights!There are always risks associated with this kind of change. Your job is to
manage the risks.

I recommend a pilot project approach. Have your supplier send you a sample
of the CSV files in addition to the normal XLS files. Continue your normal
processing, but, in parallel, start working with the CSV files. In this way,
your on-going work is not in danger, and you are able to gain experience with
the new method.
--
Gary''s Studentquot;Erinquot; wrote:

gt; Windows 2002 SP2, Office 2003 SP2
gt;
gt; I am trying to avoid potential problems with a new process and would
gt; appreciate your input.
gt;
gt; Right now we have a vast amount of data downloaded into over 200 Excel
gt; files, into a formatted style (no database-style lists - the output looks
gt; like a finished report). We refresh the data every month. We then have
gt; another template file with a macro that opens up each of these data files,
gt; imports selected sheets of data, does a save as, and moves to the next data
gt; file. We have several different computers simultaneously running different
gt; templates through this process each month.
gt;
gt; My data supplier tells me that they can speed up my data download time
gt; (which is currently about 2 weeks across 5 PCs) if they can put the data into
gt; a CSV file instead of straight into Excel.
gt;
gt; I see a lot postings about problems converting from CSV to Excel...is there
gt; anything I can do to avoid problems? Anything I need to ask my supplier?
gt; What types of problems are typical? Should I just not even consider the idea?
gt;
gt; Thanks for your insights!
gt;

Erin,

I agree with Garyquot;s Student.

Particularly because you say that the Excel files are not lists, but rather
formatted reports. I would wonder how that format is going to be maintained
in a CSV format. Also, it might be problematic using your existing
data-mining macros because they cell locations of the data within the
finished page might be difficult to sync-up with the current Excel file
formats.

These might be some of the issues you would consider investigating prior to
(potential) cut-over.

HTH

quot;Erinquot; wrote:

gt; Windows 2002 SP2, Office 2003 SP2
gt;
gt; I am trying to avoid potential problems with a new process and would
gt; appreciate your input.
gt;
gt; Right now we have a vast amount of data downloaded into over 200 Excel
gt; files, into a formatted style (no database-style lists - the output looks
gt; like a finished report). We refresh the data every month. We then have
gt; another template file with a macro that opens up each of these data files,
gt; imports selected sheets of data, does a save as, and moves to the next data
gt; file. We have several different computers simultaneously running different
gt; templates through this process each month.
gt;
gt; My data supplier tells me that they can speed up my data download time
gt; (which is currently about 2 weeks across 5 PCs) if they can put the data into
gt; a CSV file instead of straight into Excel.
gt;
gt; I see a lot postings about problems converting from CSV to Excel...is there
gt; anything I can do to avoid problems? Anything I need to ask my supplier?
gt; What types of problems are typical? Should I just not even consider the idea?
gt;
gt; Thanks for your insights!
gt;