Ark3typ3 wrote:do you think that's causing the issue?
I reckon that's likely behind it, yes.
Good to hear you got it working; however, I still think all of the information used in the table could be retrieved in a single query. That would be much more efficient by taking advantage of the database's indexes and the DBMS's ability to optimise the query, and it would also ensure that data that should be related is related. Something like (there are alternatives):
Select
t.typeName,
g.icon,
tm.quantity,
bt.wasteFactor
From
invTypes t,
eveGraphics g,
invTypeMaterials tm,
invBlueprintTypes bt,
invMetaTypes mt
Where
t.typeID = $row[materialTypeID]
and mt.typeID = $row[typeID]
and g.graphicID = t.graphicID
and tm.materialTypeID = t.typeID
and tm.typeID = mt.parentTypeID
and bt.productTypeID = mt.typeID
Although in actual fact this would be combined with the query that's producing the $materialsResult recordset.
The switch statement ("from the evePrices object") and total price calculations could potentially also be built directly into the query, reducing this loop to a couple of "fetch_assoc(); echo;" lines.