Hi Jamie

Semantics

"Jamie Collins" wrote:

"TK" wrote ...

calculations too tricky to be done using SQL
statements in a straightforward way

If you are not going to use SQL to return the recordset/Dataset
what will you use?

I read the OP's statement as meaning the calculations are too complex
to be completed solely using SQL's limited calculation functionality,
so they intend to bring some data into a workbook using SQL and finish
the calculations in Excel.

I'm sure that is what he meant, it's a semantics thing just as I said
if you are not going to use SQL to return the recordset (ADO.Net
returns a Dataset) what will you use?
and you quoted me:
If you are not going to use SQL to return the recordset/Dataset
what will you use?

I was just pointing to some alternatives, if I was making the
decision it would depend on:
1 cost
2 are we going to make changes and then outgrow
the system again if so how soon what
3 do we have the skills in house if not how much
to do the job
We haven't even considered the report generator,
Access has an excellent generator. I think most
server people still use Crystal
Forget VB6 report generator you have to use it
with the DataEenvironment and it is next to worthless
and not even supported in VB.net

I for one don't think the 2gb limit is the only issue.

Good Luck
TK