L
Leslie Porter OHV
<sigh>
ive inherited a database that is a little broken with my new job. =]
it is relational but its not. i could go into depth and detail but wont
unless its nessesary.
i have to tables one linedata the other log data.
log data is where the main information of the logs (tree's) are stored tag
number leng/diam cust and so on.
linedata is where clipping information is stored after the log is all cut
up. this is a hodge podge of machines and importing. whe it gets to the table
the tag field is soposed to be directly linked to the tag field in log data
but because of the customers there is sometimes an a b or c at the end thus
any queries i do dont link/match up. but i cant take the letters off the end
because the customer wants it that way. <ugh>
i guess the best idea that i could come up with is to add another field to
the linedata table create a query that copies the tag to it clearing any a b
c d e or f at the end (some times its that bad). but im not 100% sure how to
do this.
ive inherited a database that is a little broken with my new job. =]
it is relational but its not. i could go into depth and detail but wont
unless its nessesary.
i have to tables one linedata the other log data.
log data is where the main information of the logs (tree's) are stored tag
number leng/diam cust and so on.
linedata is where clipping information is stored after the log is all cut
up. this is a hodge podge of machines and importing. whe it gets to the table
the tag field is soposed to be directly linked to the tag field in log data
but because of the customers there is sometimes an a b or c at the end thus
any queries i do dont link/match up. but i cant take the letters off the end
because the customer wants it that way. <ugh>
i guess the best idea that i could come up with is to add another field to
the linedata table create a query that copies the tag to it clearing any a b
c d e or f at the end (some times its that bad). but im not 100% sure how to
do this.