jwcolby
jwcolby at colbyconsulting.com
Wed Jun 1 11:45:29 CDT 2011
William, > John for my benefit... How: do you do (3)? With SMO. Extremely powerful. http://msdn.microsoft.com/en-us/library/ms162169.aspx > And for a more generic solution with no guaranty of anything other than Excel, couldn't you automate this using only MS Office programs? First of all this is a "server application". It needs to run 24/7 and needs to be as robust as possible. I have a specific client for whom I do rather complex processing. I have discussed the process in past emails but let's just say I process hundreds of millions of name / address records a month, export out of SQL Server, through a third party application, and back in to SQL server. I tried to use Access and VBA as the control environment but it was just unworkable. VBA is single threaded, and some of the queries I run can take minutes to run. Back when I started this a single query could take a half hour (less powerful hardware). As a result the Access control program locks up the user interface because the single thread called out to a long running sql server query. My application has many different pieces but it will usually use threads to spin off long running processes and use flags in SQl Server tables to synchronize the parts. I moved to C# as my environment for this stuff. My application is quite complex and this specific piece is perhaps 2% of the total thing. In fact I am breaking this part out to run as a standalone application on the server running 24/7. But be that as it may, I do all of this client application in C#. I would never do it in VBA just because for this kind of thing VBA is underpowered. John W. Colby www.ColbyConsulting.com On 6/1/2011 8:23 AM, William Benson (VBACreations.Com) wrote: > John for my benefit... How: do you do (3)? > > And what would you do differently if it were MS Access? > > And for a more generic solution with no guaranty of anything other than > Excel, couldn't you automate this using only MS Office programs? >