Robert L. Stewart
rl_stewart at highstream.net
Wed May 9 08:31:00 CDT 2007
John, I am working on an example of doing this with SQL Server for you. But, since I have the same amount of free time as you do, it is going to take a week or so to complete. I am using the same concept as you did with a couple of table to hold the Import spec and the column definitions for the spec. I am going to only build it for one table to show how it can be done. The rest will be up to you if you want to expand it. Robert At 09:27 PM 5/8/2007, you wrote: >Date: Tue, 8 May 2007 13:40:59 -0400 >From: "JWColby" <jwcolby at colbyconsulting.com> >Subject: Re: [dba-SQLServer] Bulk insert >To: <dba-sqlserver at databaseadvisors.com> >Message-ID: <00d901c79198$0a703210$657aa8c0 at m6805> >Content-Type: text/plain; charset="us-ascii" > >Jim, > >At this point it is not necessary. I built a preprocessor in a few hours >using my toy (Access). My toy application handles everything exactly as >described. Someday (soon I hope) I will port that to VB.Net which I hope >will be much quicker in the preprocessing department. Then I will be >considered by some as being a real man, playing with real tools. ;-) >Others will still consider me a child, playing with toys because I didn't >take it straight to C#. SOMEDAY (far in the future) perhaps I will embed >those pieces directly in CLR programming inside of SQL Server 2005. Then I >will be able to look down my nose at those children still playing with toys. > >For now, it works and with the addition of driving the Sproc from the vba >will be an integrated application like what I described. > >John W. Colby