AnotherHiggins
Technical User
I am getting an incredibly ugly table from a company for whom we are a vendor. So I don't suppose it would be proper to call up the other company and tell them to fire the person who is sending me the offensive table....
I'm supposed validate that my company really did the work for each of these line items. I'd really like to normalize the data to make my life easier, but I'm having trouble.
I've used Skip's FAQ (faq68-5287) successfully in the past, but there are just too many headers in this monster.
Their layout contains 6 pieces of information for every part ordered. But instead of having a new row for each part ordered, they have a single row per "incident" with room for up to 10 parts (along with all 6 pieces of data for each part). This creates 68 columns instead of 19. They are doing this (I suspect) because they have a subtotal for each incident on that line. Apparently they don't visit Tek-Tips, and therefore haven't been proselytized to about the ease of reporting from properly stored data.
Following are the headers of their table:
Id like to get this down to
Any suggestions other than VBA?
[tt]_____
[blue]-John[/blue][/tt]
[tab][red]The plural of anecdote is not data[/red]
Help us help you. Please read FAQ 181-2886 before posting.
I'm supposed validate that my company really did the work for each of these line items. I'd really like to normalize the data to make my life easier, but I'm having trouble.
I've used Skip's FAQ (faq68-5287) successfully in the past, but there are just too many headers in this monster.
Their layout contains 6 pieces of information for every part ordered. But instead of having a new row for each part ordered, they have a single row per "incident" with room for up to 10 parts (along with all 6 pieces of data for each part). This creates 68 columns instead of 19. They are doing this (I suspect) because they have a subtotal for each incident on that line. Apparently they don't visit Tek-Tips, and therefore haven't been proselytized to about the ease of reporting from properly stored data.
Following are the headers of their table:
Code:
Pricing Complete (Not Implemented)
RMA Tracking #
RMA Type
KS&S Incident #
Case Number
Service Method
Account Name
Bill To Account
Actual Ship Date
FedEx Tracking No
RMA Status
Comments to Billing Dept
Item 1 Part Number
Item 1 Description
Item 1 Qty Shipped
Item 1 Qty Returned
Item 1 Unit Price
item 1 Line Total
Item 2 Part Number
Item 2 Description
Item 2 Qty Shipped
Item 2 Qty Returned
Item 2 Unit Price
Item 2 Line Total
Item 3 Part Number
Item 3 Description
Item 3 Qty Shipped
Item 3 Qty Returned
Item 3 Unit Price
Item 3 Line Total
Item 4 Part Number
Item 4 Description
Item 4 Qty Shippped
Item 4 Qty Returned
Item 4 Unit Price
Item 4 Line Total
Item 5 Part Number
Item 5 Description
Item 5 Qty Shipped
Item 5 Qty Returned
Item 5 Unit Price
Item 5 Line Total
Item 6 Part Number
Item 6 Description
Item 6 Qty Shipped
Item 6 Qty Returned
Item 6 Unit Price
Item 6 Line Total
Item 7 Part Number
Item 7 Description
Item 7 Qty Shipped
Item 7 Qty Returned
Item 7 Unit Price
Item 7 Line Total
Item 8 Part Number
Item 8 Description
Item 8 Qty Shipped
Item 8 Qty Returned
Item 8 Unit Price
Item 9 Part Number
Item 8 Line Total
Item 9 Description
Item 9 Qty Shipped
Item 9 Qty Returned
Item 9 Unit Price
Item 9 Line Total
Amount Due
Freight Charge
Code:
Pricing Complete (Not Implemented)
RMA Tracking #
RMA Type
KS&S Incident #
Case Number
Service Method
Account Name
Bill To Account
Actual Ship Date
FedEx Tracking No
RMA Status
Comments to Billing Dept
Part Number
Part Description
Part Qty Shipped
Part Qty Returned
Part Unit Price
Amount Due
Freight Charge
[tt]_____
[blue]-John[/blue][/tt]
[tab][red]The plural of anecdote is not data[/red]
Help us help you. Please read FAQ 181-2886 before posting.