Cutting List

[dennis vermeulen]

I am trying to design a cutting list program for a cupboard manufacturer.
When printing, all of the components must be grouped by color per page
e.g
Customer Job NO
Joe Bloggs 123


Color Type Length Width Qty
Maple Shelf 600 300 2
Maple Sides 1200 500 2

I have the following Table and Fields

Table1: Unit(Stores the details of the components of the unit)

Unit Type Length Width

FD400 Door 600 300
FD400 Sides 600 300
FD400 Shelf 200 200

Table2: Cutting Sheet(Calculates material required)

Unit Type Length Width Color
FD400 Door 600 300 Maple
FD400 Sides 600 300 White
FD400 Shelf 200 200 White


1.When I select the unit in the cutting sheet module, it must copy all of the records of the fields for that unit ,from the UNIT table into the fields of the Cutting Sheet Table and allow the user to change the details

2.It then prints the cutting sheets(grouped by color per page). The doors are an exception. They must be grouped together by color per page

P.S
I wish to express the same sentiments that others have already stated many times.. THE WILLINGNESS TO HELP US NEWIES IS TREMENDOUS.. KEEP UP THE GOOD WORK!!

[forskare]

RE: Cutting List

Dennis,

I think I understand what you are getting at: Joe Bloggs, Job # 123, placed an order for a cabinet. He wants a maple door, unit # FD400. If I understand, what you are looking for is that when you select unit # FD400, you want a list of the parts needed to be cut in order to make the door or cabinet. If this is the case, you should be able to use a table lookup where each unit, i.e. FD400, FD600, etc. has a list of parts stored in a child table. You might use Unit ID as a linking field.

Thus, when you select FD400, a field in the parent table, used to store the parts, looks up the parts in the child table. No doubt you would use the sam parts in other doors or cabinets so they would be linked with the same id#.

It might even work on a single table where each record contains the Unit # and the parts. I haven't tried this but I think this is the direction you would go. No doubt others more experienced than I will elaborate more or offer another apoproach. But, that's what I would try.

Hope this gives you some direction.

kenn

[dennis vermeulen]

RE: Cutting List

It seems that the units get duplicated for every unit e.g FD400 DOOR
FD400 SHELF

It means that the lookup has now a unit no for every component and means that you have to select the unit to select each component, instead of select the unit once and it copying all of the components
Dennis

[forskare]

RE: Cutting List

Dennis,

Please be a bit more specific. It would help if you would tell what you've done and how the lookup is set up. Can you attach a zip file with some instructions?

kenn

[dennis vermeulen]

RE: Cutting List

Can I send you the files?(1.5mb)That includes the Tables. Is there a way of not having to send the tables?(dbf+fpt files)
Regards
Dennis

[forskare]

RE: Cutting List

Dennis,

Click on the blue "What Files Must I Send" line that appears below the Reply window. This will give you a basic understanding of what to send.

Sometimes, all the files can be a bit intimidating so a good way to get through that is to create a new folder and copy your app to it. Then go to the control panel and delete all the tables, reports, browses and forms, etc. that are not needed.

If the file is still too big, delete some of the data since only a sample of data is necessary. Finally, zip the file and then attach it as a zip file to your reply. That way, many will have the opportunity to take a look and make suggestions.

kenn