B
Bill Raterink
Here's a challenge - Is there a way to add fields (ie.
columns) to a table DURING the Import process? I'm just
learning, & "need" all the help the import function
provides, especially the Spec part, but I also need to put
the import text file name into the first column of the
table. Some ideas I have are -
1) Import the FIRST file into a table that has one extra
col defined, then use an update query to add the file
name. How would I pass the filename from my code, to the
query?
2) Then on subsequent files, I would have to test & ONLY
add to those records in which the filename column was
blank. Would it be blank or null after the import?
3) Read the text file manually, & update each field in the
table. This would put my file name in col 1, where I
could group on it in my report, but I lose all the
automation.
4) If I MUST do the import "manually" in my code, then can
I at least save the field formats in my table so I don't
have to redefine them every time. Is this any better?
This will only be about 90 rows / 55 cols per file, 28
files per period, 1 period each, for about 80 stores. Not
a lot of data, but imports do take a few minutes, & they
are operator selected by store (which is embedded in the
file name), so there is SOME intervention.
Thanks for the help, & sorry for rambling, just trying to
get it all in one post. ; ) Thanks, -Bill.
columns) to a table DURING the Import process? I'm just
learning, & "need" all the help the import function
provides, especially the Spec part, but I also need to put
the import text file name into the first column of the
table. Some ideas I have are -
1) Import the FIRST file into a table that has one extra
col defined, then use an update query to add the file
name. How would I pass the filename from my code, to the
query?
2) Then on subsequent files, I would have to test & ONLY
add to those records in which the filename column was
blank. Would it be blank or null after the import?
3) Read the text file manually, & update each field in the
table. This would put my file name in col 1, where I
could group on it in my report, but I lose all the
automation.
4) If I MUST do the import "manually" in my code, then can
I at least save the field formats in my table so I don't
have to redefine them every time. Is this any better?
This will only be about 90 rows / 55 cols per file, 28
files per period, 1 period each, for about 80 stores. Not
a lot of data, but imports do take a few minutes, & they
are operator selected by store (which is embedded in the
file name), so there is SOME intervention.
Thanks for the help, & sorry for rambling, just trying to
get it all in one post. ; ) Thanks, -Bill.