Exporting error records to an Excel File

  • We have the following requirement for an application.

    Background:

    We have an internet application implemented using SQL Server as DB and J2EE for application front-end.

    From the front-end of the application, an action is fired which calls a stored procedure to export error records into a Excel File onto a drive mapped

    (windows drive mapping) to the SQL Server Database using "bcp".

    With this approach the error excel files are being created on the file server (above mentioned mapped drive) mapped to the database server.

    Requirement :

    The user wants to have these files on the Client PC from which the front-end application runs.

    Some of the Options we have suggested:

    Option 1:

    Generate the file on server and e-mail to user.This is done through zipping mechanisms which involves creation of few dynamic procedures which performs this dynamic zipping action and email server set-up in order email the generated file to users account.

    This can be worked out only after we decide on "sending email " functionality.

    Option 2:

    Mapping of server drive to local PC. The users will have to map the K:\ drive on the server to their PCs so that they see the files from their PC.

    This needs granting access to K:\ Drive to all the users.

    Option 3:

    FTP the file from Server to client PC.For this a new table has to be created which holds ftp address, logged userid and password.For this we need to know

    the limitations and feasibility of access of server to client PC's and client PC's to server within/outside of the P&G network.

    Question:

    Is there a way to create the error excel files on the client PC whoever is firing this action from the front-end instead of creating them on the manually mapped drive (to the DB server) on the file server ?

    OR

    Is it possible to copy/download the file created on the mapped drive to the client PC from the front-end ?

    Please give your solutions/suggestions

    for implementing this.

    Thanks

  • Hello,

    In my opinion option 1 is a bit complex, I think that you have to program Outlook to attach the file.

    Option 2 is easy but if you have more users then you will need to have more files or face locking the spreadsheet as excel is single user only.

    Option 3 FTP looks interesting except it can't be done when you make the files, you will need to modify there windows start up to copy the file to the local machine.

    Personal Choice.

    I like option 2 except for the locking part.

    NB you don't need FTP if you are copying to and from a Windows machine, just use the copy batch command.

    Have you considered using Access instead ?

    It will allow multi user (but not that many) and you can quickly add some screens.

    J

    Edited by - JulieW on 11/05/2003 04:42:38 AM

  • Appreciate your comments/suggestions.

    Thanks,

    Venkat

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply