Multiple query

[tiggy]

Good Morning (UK)

I work in the freight forwarding industry and the airlines charge us freight on weight or volume whichever is the greater.

The airline formula is LxWxH divided by 6000. If for example the actual weight is 20 kilos and the calculation resulted in 25 kilos this would become the chargeable weight.

I have made a form that is used for taking bookings and on the form I have 10 lots of the above formula (it is conceivable that there could be 100 different dimensions but 10 is about the most I can get on my form) with a total box at the bottom. Its not pretty, its not functional and I know that I should not be storing this information. Therefore please let me know how I would start to do something like the following

1. MessageBox - How many boxes i.e. 3
2. MessageBox - Length
3. MessageBox - Width
4. MessageBox - Height
(I presume that something will stop running 2,3,4 when the total of 1 (3 boxes) has been reached)
5. Result of the 3 (boxes) calculations added
6. total divided by 6000
7. result displayed
8. If possible a volume weight box field on the form filled in

Hope that makes sense

Best regards

Tig

 

[pbaldy]

From the sound of it, I would probably set it up as a continuous form/subform, so you could have as many as you needed. I think it would be better visually, since you could see all the pieces, rather than them being gathered and held in the background by input boxes. Might look like the crude example attached. You could add whatever calculations were appropriate.

 

[tiggy]

Hi Paul

Thanks, but this is similar to how I have it already on my form, apart from taking up so much room it does not allow me the flexibility to go above 10 cartons. I don't know too much about Access but I do understand that one of the principles is not to store useless information, which this does.

Thanks again

Tig

 

[pbaldy]

That's a continuous form. It will start out with one line; each time you add a record it will add a blank line for a potential new record. You can add as many records as you want (limited only by the capacity of your database). If you only added one, then only one would be stored. Here's a sample db with the form. It would probably end up being a subform of a main form that contained the booking, but I think the continuous form concept is what you're after.