Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
TXT CREATION FROM DTS SUCCESFULLY DONE 1
- Thread starter emoongq
- Start date
-
1
- #2
If the standard logging available in DTS does not work for you, then you could create a text file before your package starts (all this would be using ActiveX script task).
Then, after each export completes, use ActiveX to check for the created file's existence, and whatever else you need to check to ensure that the job is done well. You can then write a message to your log file stating if the file was successfully created or not (and why if you are feeling brave).
Hope this helps,
Alex
Ignorance of certain subjects is a great part of wisdom
Then, after each export completes, use ActiveX to check for the created file's existence, and whatever else you need to check to ensure that the job is done well. You can then write a message to your log file stating if the file was successfully created or not (and why if you are feeling brave).
Hope this helps,
Alex
Ignorance of certain subjects is a great part of wisdom
- Thread starter
- #3
Check out this forum, it is dedicated to DTS: forum961.
Here is a useful website:
I am afraid that I don't have time at the moment to walk you through setting up your package. Are you familiar with use of the ActiveX script task?
If you tell me exactly what this log should include, I can try to give you an idea on how to create it. Are you only going to be checking for the file's existence (ie not performing any sort of internal validation)?
Hope this helps,
Alex
Ignorance of certain subjects is a great part of wisdom
Here is a useful website:
I am afraid that I don't have time at the moment to walk you through setting up your package. Are you familiar with use of the ActiveX script task?
If you tell me exactly what this log should include, I can try to give you an idea on how to create it. Are you only going to be checking for the file's existence (ie not performing any sort of internal validation)?
Hope this helps,
Alex
Ignorance of certain subjects is a great part of wisdom
- Thread starter
- #5
Tks Alex, I'm not a programmer, I just made some SQL queries, this file I need is a five field file.
Export date; Export time; filename; count; balance.
I just need to put the information about 5 other previous created files. Exportation date & time, the name of the file (static field) count of registries and balance but I can leave this last in blank.
Tks a lot
Export date; Export time; filename; count; balance.
I just need to put the information about 5 other previous created files. Exportation date & time, the name of the file (static field) count of registries and balance but I can leave this last in blank.
Tks a lot
emoongq -
Here is a link to a site that shows how to check if a file exists before importing it.
You can place a task like this after your export steps to see if the file exists, and can probably create a file object (something like
dim myObject
set myObject = fso.getfile(myFileName)
) in order to get the other properties of the file once you have confirmed its' existence.
Hope this helps,
Alex
Ignorance of certain subjects is a great part of wisdom
Here is a link to a site that shows how to check if a file exists before importing it.
You can place a task like this after your export steps to see if the file exists, and can probably create a file object (something like
dim myObject
set myObject = fso.getfile(myFileName)
) in order to get the other properties of the file once you have confirmed its' existence.
Hope this helps,
Alex
Ignorance of certain subjects is a great part of wisdom
whoops forgot link ;-)
Ignorance of certain subjects is a great part of wisdom
Ignorance of certain subjects is a great part of wisdom
- Status
Similar threads
- Locked
- Question