[FX.php List] Beating a dead horse (was: trying to read back an array)

[Bob Patin]

Hi,

Well, the thing is that they can submit from multiple pages, and yes, the POST can submit a lot of items at one time (probably will almost all the time).

I've got it all working great; in addition to pulling the items in, I then have to separate them out into separate invoices, depending on manufacturer and warranty state. So I go through the array, create the 4 possible invoices, with the relevant lineitems on each... 

Best,

Bob Patin



Longterm Solutions
bob at longtermsolutions.com
615-333-6858
http://www.longtermsolutions.com
iChat: bobpatin
FileMaker 9, 10 & 11 Certified Developer
Member of FileMaker Business Alliance and FileMaker TechNet
--
Expert FileMaker Consulting 
FileMaker Hosting for all versions of FileMaker
PHP • Full email services • Free DNS hosting • Colocation • Consulting


On Sep 20, 2010, at 11:19 AM, Joel Shapiro wrote:

> You might have figured this out already, but here are some thoughts of mine:
> 
> What's the session array supposed to be capturing?  Is it individual items that need service, with data specific to each of those items (serial, type, description, etc)?
> 
> Are users sending more than one item per POST?  What does the $_POST['recid'] array look like?  And if recid's are in an array, why doesn't the other data come in with them in the same array (it looks like they come in as $_POST['description12'], $_POST['description213'], etc.)
> 
> I think the goal would be to end up with a $_SESSION array like this, containing an [item] array ($_SESSION['item']):

-------------- next part --------------
Skipped content of type multipart/related