WTF-y possible workaround for #3: when your code is called, move some of the 3rd party data off-chip and use that memory. Just re-load that data before returning. Depending on how much memory access your function does, it might well be faster than putting your stuff off-chip.

[quote user="AccessGuru"] Well, if you ever wanted to move to a database, at least orders.inc should be easy to parse and convert to SQL insert statements. The biggest problem with this is the memory usage and lack of concurrent reading/writing. I don't think it's horrible, if you think...

[quote user="Iago"] Does all the text really have a pale outline, or is it just that your camera is "helpfully" trying to "enhance" the picture? (These haloes and suchlike are painfully common these days. Most people seem not to notice them, but once you start, you'll...