S
Steve
Folks,
I've been directed to create the new pricebooks for my company, and I'm
stuck trying to figure out the best way to do this. In fact, I'm stuck
trying to figure out any manageable way to do this ;-)
In the past price books were fairly simple reports we output from an access
database we created. Earlier this year I redid that database to allow us to
create different versions of the book for different recipients. Since then,
someone proposed a new format that is better, and we need to incorporate it.
The new format has a summary table for each product, and this table varies
in dimensions for each product and for each product's application - we make
capital equipment for the graphic arts industry. Following this table is a
reference section listing the actual pricing items that have been totaled
for each intersection in the table. Following the reference section, there
is a list of options, and some of those will have photos or other
illustrations. We have about 30 price book recipients who will receive a
custom-tailored version, which is to say the tables, reference sections and
options can be different for each recipient. There are about 200 products,
maybe 20-30 needing the new format - the others will done in the old format.
It's fairly easy to create the necessary tables in excel, but I can't figure
out how to get them into access as an OLE object without manually pasting
them in each record - which is unmanageable given how many there are. Also,
linking each reference section to the appropriate table is a problem. I know
I can pound this all out manually in Word, but god help us if we need to
make changes and propagate them through all the versions. I've also thought
of doing the entire thing in Excel, but page formatting becomes a problem. I
think the ultimate solution is to have a word doc where I can specify what
book is being made, read the book contents out of Access, pull the tables
out of Excel (which in turn pulls pricing from Access) and then save each
doc as it is created. But even this would mean making 30 new docs every time
changes are made...
Has anyone done anything similar? Have any advice?
Thanks!
Steve
I've been directed to create the new pricebooks for my company, and I'm
stuck trying to figure out the best way to do this. In fact, I'm stuck
trying to figure out any manageable way to do this ;-)
In the past price books were fairly simple reports we output from an access
database we created. Earlier this year I redid that database to allow us to
create different versions of the book for different recipients. Since then,
someone proposed a new format that is better, and we need to incorporate it.
The new format has a summary table for each product, and this table varies
in dimensions for each product and for each product's application - we make
capital equipment for the graphic arts industry. Following this table is a
reference section listing the actual pricing items that have been totaled
for each intersection in the table. Following the reference section, there
is a list of options, and some of those will have photos or other
illustrations. We have about 30 price book recipients who will receive a
custom-tailored version, which is to say the tables, reference sections and
options can be different for each recipient. There are about 200 products,
maybe 20-30 needing the new format - the others will done in the old format.
It's fairly easy to create the necessary tables in excel, but I can't figure
out how to get them into access as an OLE object without manually pasting
them in each record - which is unmanageable given how many there are. Also,
linking each reference section to the appropriate table is a problem. I know
I can pound this all out manually in Word, but god help us if we need to
make changes and propagate them through all the versions. I've also thought
of doing the entire thing in Excel, but page formatting becomes a problem. I
think the ultimate solution is to have a word doc where I can specify what
book is being made, read the book contents out of Access, pull the tables
out of Excel (which in turn pulls pricing from Access) and then save each
doc as it is created. But even this would mean making 30 new docs every time
changes are made...
Has anyone done anything similar? Have any advice?
Thanks!
Steve