>> What we did was figure out a little Jet (aka "Microsoft Access") database
>> table he could use as input to his "packing slip print"
>> routine (LabelView or BIQuery or some kind of report writer with which my
>> client is pretty handy )
> I think what is causing me the most confusion is how to store this stuff in a
> way that's easy to write out from the mapper, yet
> still easy to query via SQL, since >the pack slips are probably going to be
> created in Bartender. ..
I cheated, kinda. I had the client design the database "to make it easy for
you to create packing slips."
Turned out he wanted that DB a whole lot simpler than I would have made it.
The Fringe Benefit is, of course, the USER actually gets involved with the
design of software for HIS USE. ( Involved Users? What a
Concept!)
Regardless, I just don't believe in making things easy for the software
developer, I believe in making things easy for the user. If
I can't give the user what he wants he should get another developer.. and I
have told my clients that. I WANT them to 'THINK BIG' .
MCM
------------------------------------
...
Please use the following Message Identifiers as your subject prefix: <SALES>,
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Job postings are welcome, but for job postings or requests for work: <JOBS> IS
REQUIRED in the subject line as a prefix.Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/EDI-L/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/EDI-L/join
(Yahoo! ID required)
<*> To change settings via email:
[email protected]
[email protected]
<*> To unsubscribe from this group, send an email to:
[email protected]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
