Inventory Management Administration II -

I'm following the Inventory Management Administration tutorials and in Inventory Management Administration II, section 11 and 12, I've changed my select statement on my Inventory Update page to the following...

SELECT LEDid, LEDtitle, LEDmetadesc, LEDproductcode, LEDimgtmb, LEDstock, LEDProductUpdateDate - (SELECT Coalesce(SUM(LEDDetailQuantity),0) FROM LEDorder INNER JOIN LEDdetail ON LEDdetail.LEDDetailOrderID = LEDorder.LEDOrderID WHERE LEDOrderDate > LEDProductUpdateDate AND LEDDetailLEDid = LEDid) AS RemainingInventory FROM LEDprods WHERE LEDid = %s

Now, whenever I try to display the LEDProductUpdateDate on the page, to show the client when the stock was last updated, like so:
<?php echo $row_rsEDITSTOCK['LEDProductUpdateDate']; ?>]

..I get the following error:
Notice: Undefined index: LEDProductUpdateDate in /home/led2014/public_html/ledADMIN/editstock.php on line 306

I've triple checked that I've followed the tutorial correctly and I have renamed all of the fields to match those of my own Order and OrderDetail tables and everything is in order.

Why the error?

NJ

<sigh> In section 11 in the tutorial it states...

"11.Copy the following snippet of code (Ctrl or Cmd + C):

- (SELECT Coalesce(SUM(DetailQuantity),0) FROM orders Inner Join orderdetails ON orderdetails.DetailOrderID = orders.OrderID WHERE OrderDate > ProductUpdateDate AND DetailProductID = ProductID) AS RemainingInventory

12. Paste the snippet into the Recordset (Ctrl or Cmd + P) :"

What the tutorial fails to mention is that the "-" symbol is being used to do a calculation using the stock field in the database so you MUST place this snippet immediately after the stock field in your recordset.

Easy when you know how - bloody difficult to fathom when you don't.
NJ

The screen shot in step 12 shows where the snippet should be placed.

I Will forward a request to the documentation team to include a before and after image

It's nothing to do with the graphics, it's the understanding that a calculation is taking place using the recordset's "stock" field, which is why it needs to be placed where it does - directly AFTER the stock field.

Like I say, it's easy this stuff when you have the know how, but without the know how there's a little more hand holding required, at least for me anyway.

Still nothing from Ray btw.
Thank you.
NJ

I understand, Nathan, which is why I indicated that I would forward the info to our documentation team to have them clarify the step.

I have forwarded your other thread to Ray, and asked him to contact you.