> I have many data files containing data from our old system. I have 12 filenames
> to deal with (1 file per table). I have 5 cycles (we sell utilities) each
[quoted text clipped - 41 lines]
>
> Tom

Signature
Steve S
--------------------------------
"Veni, Vidi, Velcro"
(I came; I saw; I stuck around.)
>> I have many data files containing data from our old system. I have 12 filenames
>> to deal with (1 file per table). I have 5 cycles (we sell utilities) each
[quoted text clipped - 45 lines]
>
>What is the structure of the "old" data files (tables)?
The data is from a Data General DBAM file structure, maintained by a
process called INFOS. (Didn't help you any, did it?)
I've already extracted all my data, into one text file for each table
I want to create. It's comma delimited, with *everything* enclosed in
quotes. I have one set of files for each book. (See last answer.)
Plus, I actually have two identical databases. One was "live" and the
other "history". So I *actually* have to cycle thru 100+
books...TWICE.
>And what format (text files, dbf,...)?
Already answered.
>What is the structure of the new Access table?
Why?
>Have you thought of using an Append Query? Maybe to a temp table that you
>could do some massaging of data, then appending to the main table? Or even
[quoted text clipped - 5 lines]
>Much less involved that using arrays.... there are wizards to help import
>the "old" data tables.
I didn't mention arrays to massage the old data. I do *NOT* need to
play with my data. I've already taken care of that. I have all my
import spec files created. I was [merely] looking for an easy way of
cycling thru all the meter books, which is my lowest breakdown
(grouping) of my data.
4 cycles * 25+ meter books per cycle = 100+ meter books to cycle thru.
>HTH
SteveS - 28 Jul 2005 17:05 GMT
> >> I have many data files containing data from our old system. I have 12 filenames
> >> to deal with (1 file per table). I have 5 cycles (we sell utilities) each
[quoted text clipped - 83 lines]
>
> >HTH
Tom,
I asked about the Access table structure because I was wondering if the data
was in a "flat file" format and if you were going to convert it to a
relational model. When I used "massaging", I meant that if you had a seperate
file for each year, maybe you were going to add a new field for Book/Cycle
year; once a (text) file was in an Access table, you could run an update
query to add the year to the records.
When importing a text file, you have the option to specify what data type
the the import field is. I think using the Import command is easier than
writing a sub to do the importing/ data type conversion, although I've done
both.
Anyway, it was the way I handled it when I to convert about 50 DBF files
where the data had been exported as text.
Good luck...

Signature
Steve S
--------------------------------
"Veni, Vidi, Velcro"
(I came; I saw; I stuck around.)