Re: Use the input to an Access 2003 form as parameters to a SQL Server stored procedure

On Thu, 29 Sep 2005 23:48:49 GMT, fumanchu <leondobr@xxxxxxxxxxx>
wrote:

You want fast and dirty: install the SQL Server Client Utilities on
the user's workstation. Among other things, this installs Query
Analyzer. You can create a .SQL file that the user can load into this
app, enter the values for a few parameters, and click the button to
run the sproc.

Slow and clean? Create an Access ADP (data project) to handle this
using a form and calling the sproc over ADO.

-Tom.



>I've got to let end users (really just one person) load billing batch
>files into a third party app table. They need to specify the billing
>cycle name, the batch name, and the input file name and then I can use
>these values to execute a SQL Server stored procedure to load them
>into the batch table from the input file (the stored procedure uses
>Dynamic SQL to Bulk Insert the file to a temp table then processes it
>into the final table.)
>
>My first idea was to give them (really just one person) an Access form
>front end to a linked table in the SQL Server database and let them
>input the three values into that linked table. Then I could run the
>stored procedure from an insert trigger on the table on the SQL
>Server. Unfortunately, you can't run Bulk Insert from a trigger.
>
>I can't think of any other way to do it. The non technical end user
>has to be able to fill in the three values somehow and kick off the
>SQL Server stored procedure.
>
>Any ideas? Fast and dirty is fine.

.

Quantcast