Viewing 15 posts - 2,776 through 2,790 (of 3,738 total)
As stated you can use SSIS.
An SSIS For Each Loop Container and a Script Task with the File System Object will do it.
June 29, 2011 at 5:26 pm
So what is not not working? How can we be of assistance to you?
June 29, 2011 at 10:51 am
Simon_L (6/29/2011)
Pointers/Help/Words of wisdom if you pleaseIs it possible to use policy management to ensure/check all triggers and fks are enabled ?
many thanks
si
If you create a trigger or a...
June 29, 2011 at 10:44 am
If you add a breakpoint on the Line of Code and place the mouse over the "Source_File_Path" it should display the path of the Access Database that you opened.
June 29, 2011 at 9:33 am
clarmatt73 (6/29/2011)
This is the line where the error is occuringSet rstFilePath = CurrentDb.OpenRecordset("Source_File_Path")
The ("Source_File_Path") should be the path of the Database that you currently have open.
June 29, 2011 at 8:24 am
'\\sqldump01\prisql01\' does not sound like a valid Server & Path (Share).
June 29, 2011 at 8:08 am
As was suggested the files would be moved from the location that you are transferring them from.
June 28, 2011 at 1:35 pm
You may want to read the following article:
Forum Etiquette: How to post data/code on a forum to get the best help
http://www.sqlservercentral.com/articles/Best+Practices/61537/
June 28, 2011 at 12:48 pm
Try the following URL which has some links to articles that may be of help to you.
June 28, 2011 at 12:46 pm
I can't think of a reason that would necessitate SSIS.
The following link has some simple examples of Dynamic SQL.
http://www.sqlteam.com/article/introduction-to-dynamic-sql-part-1
June 28, 2011 at 12:17 pm
Have you considered storing the recipients and the Where Conditions in Tables and dynamically generating the SQL Statements?
June 28, 2011 at 11:51 am
If the Indexes are heavily fragmented you will achieve better results by rebuilding the index as opposed to Reorganizing the index.
June 28, 2011 at 10:26 am
Post removed.
June 28, 2011 at 9:54 am
Parveen-288612 (6/24/2011)
"\etworklocation
Is not a valid UNC Path.
Also make sure that the SQL server Agent Account has permissions to the correct path.
June 28, 2011 at 8:12 am
Viewing 15 posts - 2,776 through 2,790 (of 3,738 total)