code to create the tables in the mdb. Once you have the tables, then
procedure. Basically the more layers of API you have, the slower it's
200,000 rows, then you can expect to wait a while.
On 12 Sep 2006 07:26:13 -0700, santhoshks@gmail.com wrote:
>Hi thanks for the reply.
>I am already using the interop assembly to write into .mdb.
>my problem is when i used the interop assembly, i need to create the
>access object first and then insert my dataset into the Access table.
>When the number of records is very high e.g. around 200,000 the time
>taken to insert the dataset into the access table is over 45
>mins..Instead i want to use the Access object which is available in DTS
>packages because when I tried to write into .mdb using the access
>object in DTS package, the same 200,000 records got inserted int 5 mins
>which is because SQL makes use of the data link object to write into
>MS-Access.
>
>The problem now i have in front of me is when i perform a DTS task to
>write the query output to a .mdb file, I cannot use stored proc in its
>direct form as the output columns of a stored proc wont be available to
>create the table in MS-Access but when the query is executed directly
>the output columns are automatically created in the MS-Access table.
>
>Regards,
>Santhosh
>
>Mary Chipman [MSFT] wrote:
>> The fastest way to get stored procedure output into an Access mdb is
>> by using a pass-through query. These can be manipulated by setting a
>> DAO.QueryDef's .SQL property to a T-SQL "EXEC MyProc param1, param2"
>> statement. DAO is available to your C# code by using the Office
>> primary interop assemblies (PIAs) available at
>>
http://support.microsoft.com/kb/328912. >>
>> --Mary
>>
>> On 8 Sep 2006 13:55:05 -0700, santhoshks@gmail.com wrote:
>>
>> >I have a stored procedure which upon execution, the output needs to be
>> >wrote onto a .mdb file..i need to do this as writing it through
