Re^3: Spreadsheets, HTTP::Recorder and interactivity

Absolutely true. However, I will still maintain that a spreadsheet wasn't meant to be batched. If it was, then they are nothing more than extremely simplistic versions of Access.

------
We are the carpenters and bricklayers of the Information Age.

Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose

I shouldn't have to say this, but any code, unless otherwise stated, is untested

Comment on Re^3: Spreadsheets, HTTP::Recorder and interactivity

Replies are listed 'Best First'.
Re^4: Spreadsheets, HTTP::Recorder and interactivity by tilly (Archbishop) on Jul 01, 2004 at 19:01 UTC
We are close to being in perfect agreement. No, spreadsheets were not meant to be batched, which is part of the reasons that attempting to use them in batch processing runs into problems. However I'd also maintain that Access, and applications used in Access, are also not meant to be batched. As a sample indication of why, consider the tendancy for issues to cause a pop-up to appear which practically demands human intervention. (You can get around that with Win32::GUI, but layering hacks on hacks like that is again fragile.)	[reply]

Replies are listed 'Best First'.

Re^4: Spreadsheets, HTTP::Recorder and interactivity
by tilly (Archbishop) on Jul 01, 2004 at 19:01 UTC

However I'd also maintain that Access, and applications used in Access, are also not meant to be batched. As a sample indication of why, consider the tendancy for issues to cause a pop-up to appear which practically demands human intervention. (You can get around that with Win32::GUI, but layering hacks on hacks like that is again fragile.)

[reply]