Please see my reply to your other exact same post titled "FilePath variable"
--
----------------------------
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"TomTait747" <TomTait747 (AT) discussions (DOT) microsoft.com> wrote
Quote:
Allan,
The example at the URL does look like exactly what I asked for,
however I'm not sure I know how to use it (plus it implies it's for a SQL
|
Server version beyond 2000). However, to let you understand why I can't
take advantage of that, let me say that I have about six years of Access and
reasonable but not expert VBA skills. My experience with DTS is limited to
what can be create with the DTS import wizard. I did manage to get the
wizard to make a procedure with the sub Main and all that, but nothing
happened when I ran it from Access 2000, it compiled, and no errors were
thrown so it's hard to know what the problem is.
Quote:
I've created the *.dts file you put on your hard drive and have
found code to execute it from Access VBA. I've also managed to create a
|
package and leave it in the local package folder within Enterprise Manager.
And I've gone to the diagram within the package and found the place where
the file-to-import path/filename is.
Quote:
Maybe part of what I need to know is what to replace the path with
so that the package knows to use the variable that I pass to it. The DTSRun
|
route with the /A sounds the most promising of the two options you've
discussed, especially if I can launch DTSRun from the SQL Analyzer via
pass-thru query. I look forward to your response. Thanks!