We build a product with +600 different configurations, therefore +600 different part numbers.
My database has a table, primary key "part number" with all the different options checked or unchecked in each record. One report looks at options, determines option locations and displays/prints out all configurations, each page representing a unique part number. This has been our product "bible".
We have a product called "DocTrak" which works with our ERP system. When we print a job from the ERP system we can link the part number to a specific file or set of files with DocTrak, which then get printed with the job paperwork.
So, what I need is code behind a pushbutton that will look at the first record (part number), run the report for just that record, save the report as a one-page snapshot to a specified location on our public drive, move to the next record, repeat process.... until it saves all 600+ as 600+ files in a directory on our public drive.
That way we can specify what .snp file to print when we print an ERP job using DocTrak. When the job gets printed, Snapshot Viewer prints the one-page configuration from the linked .snp file. Assemblers now do not have to wade through 600 pages of configurations.
Does this make sense? Can you help? Thanks!
My database has a table, primary key "part number" with all the different options checked or unchecked in each record. One report looks at options, determines option locations and displays/prints out all configurations, each page representing a unique part number. This has been our product "bible".
We have a product called "DocTrak" which works with our ERP system. When we print a job from the ERP system we can link the part number to a specific file or set of files with DocTrak, which then get printed with the job paperwork.
So, what I need is code behind a pushbutton that will look at the first record (part number), run the report for just that record, save the report as a one-page snapshot to a specified location on our public drive, move to the next record, repeat process.... until it saves all 600+ as 600+ files in a directory on our public drive.
That way we can specify what .snp file to print when we print an ERP job using DocTrak. When the job gets printed, Snapshot Viewer prints the one-page configuration from the linked .snp file. Assemblers now do not have to wade through 600 pages of configurations.
Does this make sense? Can you help? Thanks!