Thanks. That did it.

Sam

Is the question how do you call a stored procedure from Access? THis should do it:

Public Function InsertDate( _

        strTableName As String, _

        strStartDate As String, _

        strEndDate As String, _

On Error GoTo...

This really helps. Thanks. My takehome lesson is use grouped names only after careful thought and consideration of multiple factors. I decided not to use a prefix for now.

Sam

mkeast, thanks for bearing with me. I'm a newbie and truly baffled by this. This statement executes properly from QA:

EXEC sp_generate_inserts OccRadiology, Fact, @debug_mode=1, @cols_to_include ="'AilmentID','Ipsil','ContraB'"

debug_mode is bit type (so...

here is the statement printed with print @cmd:

osql -S. -E -dRestructureTest -Q"EXEC sp_generate_inserts 'OccRadiology','Fact',@debug_mode=1,@cols_To_Include='Ipsil','Contra' -w8000 -h-1 -o c:/Artifex/inserts.sql

Sam

okay, it looks like the above solved the issue with the @col_to_include parameter.

Now I have this error: Line 1: Incorrect syntax near '-'.

There are many dashes. How do I find...

thanks. I finally found it. sorry for the trouble.

Sam

Thanks. That really helps.

Sam

Mike: Thanks so much. This is really helpful.

Sam

Clarification, Mike:

You’re saying that

Set rs=CurrentProject.Connection.Execute(strSQL)

Is faster than

Set rs=New ADODB.Recordset

Having perused the responses, I find my fingers itching to send my own little opinion. 🙂

I live in a different world (non-IT) and have been investigating for a couple...