Rachel,
Did all that just (here and now) say something like:
we're starting with a clean sheet of paper, will use everything we have
learned, and will not encumber our targeted functionality with issues of
backward compatibility
?
Regards,
Jim Cunningham
P.S.
I don't mind, as I scan in the tables and pipe them thru a
(new/additional/connectable) rDb file/table, field, generator anyway. All I
then have to do is create the proper indexing to then fire my
cascading-browsers generator (it keys off "of" relationships) and then I
apply can-read/write/update permissions in the data dictionary for the
general case (it has to be customized for each site/partner anyway; hey! why
didn't I automate that to(sic)? a Q&A script) to disallow user
browsing/clobbering system/case/sequence/document/table fields that are for
organization etc.; not user input.
But some other people will then need clean sheets and lots of time and money.
Some more than others. But it's always been like that.
I suppose OO-edi really must insist on the best overall state of the art;
duty huh?
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
