record sorting

[Guest]

newbie quetion, please have patience.

I'm trying to use VB to go through a table of bills of material and compare
the attributes of the end items with the attributes of it's components to be
sure they match.

IT sends me a text file with the BOMs, record 1 is end item #1 , next 40
records are #1's components. Record 41 is end item #2, next 40 records are
#2's compnonts etc, etc.

I imported this text file to a table with an autonumber field, end
item/component sequence is OK. (Access 2000)

Then tried using a make table query (to create a new table with extra fields
for errors) and loop through this new table to identify errors. When an
error is found - end item and offending component are written to the extra
fields.

Well ... I see now that the make table query doesn't preseve the record
sequence of the original table (right?) so my end item/compnent relationship
is lost.


My question is can I use VB to sort my new table to re-establish the record
sequence? Or should I start over with a better approach?

Many thanks

 

[missinglinq via AccessMonster.com]

I'm not really clear exactly what you're doing here, but it sounds as if,
when you're importing your data, you're importing it into one table and using
some records for "end items" then some records for "end item components."
You're mixing apples and oranges! This makes no sense to me. The components
should either be a part of the "end item" record in your single table, or in
records in a separate table connected to the original table by the "end item
#."

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000

Message posted via AccessMonster.com

 

[Guest]

missinglinq ,
Our text file originates from a paper report, we have the option to print it
to a .txt file. This it is a problem, but it's what I have to work with.

The data comes to me is like this.

record 1 - parent
record 2 - child
record 3 etc - child
record 100 (or 200 ...) parent
record 101 etc - child

Each parent (end item) can have 100-200 component (child) items.

If I can preserve the sequence of the text file I can loop through and
recognize parent (blue), component (blue, blue, blue, red ... error!) and so
on.

The data is dynamic, changing every day as new items are structured and
changed by engineering. The errors are killing us. Yesterday I had 550,000+
records so I'm looking for an automated solution.

Thanks for your help (it's a big cat)