Newbie Question - best practices

[Elliott]

I am writing an application for a client which will use as its data files she prepares from another system.  I'd like to automate the process as much as possible, putting the responsibility of cleaning the data back on her.  Does it make any sense to use a file upload to build the table(s) if the data in the file(s) being uploaded needs to be edited?  Is the right way to handle the file creation is to upload (and process) the file(s), splitting it into good data and data needing additional massage to be added.

thanks
Marianne

[Genady Sergeev]

Hello Marianne Seggerman,

Could you please clarify what is the use case you want to achieve? How would you determine which is the 'bad part' of the file and which is a good one?

Kind regards,
Genady Sergeev
the Telerik team

[Elliott]

If I am making more of an application design question I apologize in advance.  The user is providing files to build a table of items to sell.  These items will be used to populate an SQL table.  This past year we had problems with incomplete data - blank descriptions, inaccurate case packs, etc.  All the file upload control / process does is to pull a file from the server to the client, right?  The process of validating the data, creating an error repository and managing the error correction process - this all happens later.  I think I am confusing file upload as a systems process with your FileUpload control, like one control will magically edit and correct the data.  Even adding the correct records to the table is not the work of the FileUpload control.  All it does is find one file and put it somewhere.  It cannot do any validation of the actual content of the file being processed.

[Cori]

Hello Marianne,

That is correct, the RadUpload control only uploads the file to a folder you want it saved to. It will not transform the data from the file into SQL tables. You'll need to do that yourself.