Question in .vbs script to pull export from Access

[Blake Patterson]

I have a .vbs script that I'm running from the Windows destkop (intend
to have it run by Windows' task scheduler) to pull an export from MS
Access. Here's the script:

' *************** ***********
dim objAccess
Set objAccess = CreateObject("A ccess.Applicati on")

ObjAccess.OpenC urrentDatabase( "C:\codescratch \db1.mdb")

ObjAccess.DoCmd .TransferText acExportDelim, "Expout Export
Specification", "table1", "C:\expout.txt" , False, ""

ObjAccess.Close CurrentDatabase
Set ObjAccess = Nothing

MsgBox "Script has finished running."
' *************** ***********
....in this code, "Expout Export Specification" is an export spec I
defined in Access for this simple, 3-col. test table. Using it to
export from within Access works fine.

I get no errors in this script, but the output file is not updates
when this is run. No write to that file takes place. I am required
to have some kind of file present on the filesystem at, in this case,
C:\expout.txt or the script complains that it can't find the file.
That seems odd to me. But again, the file is not updated.

What am I doing wrong? Thanks!

bp

[Pieter Linden]

This won't automatically overwrite the existing file, I don't think.
You'd have to put a kill statement in your code before running the
export to delete the existing file first.

something like:

Public Function ExportFile()
On Error Resume Next

Kill ("C:\MyTestExpo rt.txt")
DoCmd.TransferT ext acExportDelim, "MySpecificatio n", "MyTable",
"C:\Test.tx t", True
End Function

[Blake Patterson]

In article <bf************ **************@ posting.google. com>,
pi********@hotm ail.com (Pieter Linden) wrote:

This won't automatically overwrite the existing file, I don't think.
You'd have to put a kill statement in your code before running the
export to delete the existing file first.

something like:

Public Function ExportFile()
On Error Resume Next

Kill ("C:\MyTestExpo rt.txt")
DoCmd.TransferT ext acExportDelim, "MySpecificatio n", "MyTable",
"C:\Test.tx t", True
End Function

Hmm...

As I understand, the TransferText method does indeed overwrite the file
if it is present. It is odd to me that it must be present or I receive
a file-not-found error, as well.


bp

--
Heisenberg may have slept here.