T
Tokyo Alex
Dear all,
Is it possible in Access 2007 to create a delimited-data export
specification that is independent of the source table structure?
For example, if I want to export to a text file with a delimiter | and a
text qualifier of # (instead of the default , and "), I can create a spec to
allow automation of the task with TransferText.
However, if the table I use to create the spec has 7 fields and I try to
apply the spec to a different table with 8 fields I get a "The Microsoft
Office Access database engine could not find the object 'Filename#csv'. Make
sure the object exists and that you spell its name and the path name
correctly," error. (Aside: Least helpful Access error message *ever*)
Is there anyway to bypass this so that I can use code to cycle through an
array of export tables without having to specify a different spec for each
table?
Thanks,
Alex.
Is it possible in Access 2007 to create a delimited-data export
specification that is independent of the source table structure?
For example, if I want to export to a text file with a delimiter | and a
text qualifier of # (instead of the default , and "), I can create a spec to
allow automation of the task with TransferText.
However, if the table I use to create the spec has 7 fields and I try to
apply the spec to a different table with 8 fields I get a "The Microsoft
Office Access database engine could not find the object 'Filename#csv'. Make
sure the object exists and that you spell its name and the path name
correctly," error. (Aside: Least helpful Access error message *ever*)
Is there anyway to bypass this so that I can use code to cycle through an
array of export tables without having to specify a different spec for each
table?
Thanks,
Alex.