| |
On Thu, 8 Jul 1999 17:29:24 GMT, "Robert Munafo" <munafo@gcctech.com>
wrote:
> I don't think you'll be able to use Excel macros to do the type of processing
> that inventory work requires. You need a programming language that includes
> native string data types, grep-style regular expression pattern matching, and
> associative arrays. It also helps if the language can invoke shell commands and
> access the filesystem directly. The only platform and language I have found
> that comes anywhere close to doing all this is perl running on Unix.
My point was that it would be useful for people to be able to use the
inventory data in as many different ways as possible. For a lot of people,
using the data means opening a list in Excel. Non-techies need data in
better formats than programmers. Programmers can code around deficiencies
in the data format. Excel users can't.
> I also don't see the point in posting my data in a format that is designed with
> machine-readability as its highest priority. The machine should work harder,
> not the human. My Perl scripts have no problem reading the format I'm using and
> they can automatically detect the formats other people are using. So why not
> use a format that's easy for people to read. Most people don't need to read the
> data into a database, they just want to find out how many 2x3 inverted roof
> bricks they'll get if they go out and buy the set.
The point is to use a format that both humans and their software tools can
use.
> I like your ideas about using column headers. I haven't seen inventories that
> put the type and size in seperate columns, but that's a good idea that lots of
> people will want to use. I can't just do count-color-description alone, I need
> to add a 4th column for "ID"/part number.
Todd Lehman posts inventories with size and description in separate
columns, and his AucZILLA database is the same (but the lists on the
AucZILLA site have the two columns run together).
> But my inventories do start with
> column headers.
Mine don't, and they should.
I'm going to look at my inventory tool (an MS Access app, eek!), and change
the data around to separate size and description. And add those pesky
column headers on the output.
Steve
|
|
| |
> I'm going to look at my inventory tool (an MS Access app, eek!), and • change
> the data around to separate size and description. And add those pesky
> column headers on the output.
You think an MS Access app is bad? How about MS Works? :o) I know, I
know, but it came pre-installed! :)
--
Cheers ...
Geoffrey Hyde
--
www.fastinternet.net.au/~ghyde
--
|
|
|
