Forum Moderators: open
I can already see the potential for major headaches if data is wrong, or something else screws up, but it's the way "it's been decided" to do it before I got the task.
First of all.... is that the best option, or would an excel to xml to db method be better?
Second of all, is there a component that will do this?
Third of all, would it be easier to write it in VB as a component to do this?
Fourth of all, why do technical decisions get made before the technical people get involved? :)
(The first 3 questions are more important though)
The error handling just needs doing appropriately, its not necessary a big problem.
2) Yes an ADODB.Connection supports excel & sql 2K and Scrpting.Filesystem supports csv & text file reading - both components should be already avilable to you. If the excel files are at the client you may need an additional 3rd party upload component.
3) Yes if you want to hide the implementation from the asp code and yes if the filesize/frequency demand higher performance than a pure script gives.
4) Because they dont distinguish between system requirements,logical design and physical design!
so, let's say I choose the ADODB.Connection option. Would it pan out like this:
1. Upload file
2. Set up connection to spreadsheet
3. Import data to a temp table
4. do data processing stuff into proper tables
5. either delete or archive spreadsheet
6. job's a goodun
I've been doing asp for a while but haven't used it with ms office at all, so it's a bit new to me
