Team,
A bit of background first. We sell watch straps as well as batteries. These watch straps for a single type come in various sizes, colours and buckle offerings.
Let's say we have a leather strap available in two sizes. I give it a product code of LS (for leather strap) and then I give that product a component and the options required. Okay so far... now I want to control my stock (feeding into Sage), So when someone selects a LS which is Black I need the stock to decrement by one black LS strap. So I assume I have to create a product reference for every single combination (so that for each particular combination I can put the correct product code against the permutations tab under the component)?
I am okay with this so far.
Now here is the rub. We have approximately 20 different strap types, some with about 40 permutations per strap type. I wanted to apply the product code to each of the valid permutations without having to go through the ball ache of doing this via the permuations tab for each of the generic product codes.
I looked in the Access tables (I am quite confident using Access) and sussed out that the options are of the form 234;245,256;248 which is the option type;option value for each combination. What better way, I thought,than to write a table update query to interpret these values and give the apporpriate product code. I can't. Access doesn't behave. I can't manipulate anything it would seem. I can export the table to a separate database and do what I want there, but not in the actinic.mdb. Why not?
If I do something like Prop:Mid([<string which defines the options>],5,3) to get the first property value (expecting to return 245 in the example above) I just get an #error.
So as a general question, can I use Access to manipulate data as I would any other Access database?
Has anyone else had to go through assigning large numbers of product codes to different permutations? If so how?
Ad<Thanks>vance
Andrew
A bit of background first. We sell watch straps as well as batteries. These watch straps for a single type come in various sizes, colours and buckle offerings.
Let's say we have a leather strap available in two sizes. I give it a product code of LS (for leather strap) and then I give that product a component and the options required. Okay so far... now I want to control my stock (feeding into Sage), So when someone selects a LS which is Black I need the stock to decrement by one black LS strap. So I assume I have to create a product reference for every single combination (so that for each particular combination I can put the correct product code against the permutations tab under the component)?
I am okay with this so far.
Now here is the rub. We have approximately 20 different strap types, some with about 40 permutations per strap type. I wanted to apply the product code to each of the valid permutations without having to go through the ball ache of doing this via the permuations tab for each of the generic product codes.
I looked in the Access tables (I am quite confident using Access) and sussed out that the options are of the form 234;245,256;248 which is the option type;option value for each combination. What better way, I thought,than to write a table update query to interpret these values and give the apporpriate product code. I can't. Access doesn't behave. I can't manipulate anything it would seem. I can export the table to a separate database and do what I want there, but not in the actinic.mdb. Why not?
If I do something like Prop:Mid([<string which defines the options>],5,3) to get the first property value (expecting to return 245 in the example above) I just get an #error.
So as a general question, can I use Access to manipulate data as I would any other Access database?
Has anyone else had to go through assigning large numbers of product codes to different permutations? If so how?
Ad<Thanks>vance
Andrew
Comment