The beauty of the solution I implemented is that RJS stores the actual
address and name of the document in the iSeries. It was easy to use SEQUEL
to then retrieve the documents for the customer.
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Stone, Joel
Sent: Thursday, November 01, 2012 11:14 AM
Subject: RE: datalink columns
My company uses Webdocs from RJS.
Storing docs in the IFS is simple - compared to the hard part which is
document retrieval and tying docs to your database.
Pretty soon users will want to retrieve invoices by invoice #, and then by
client#, and by bill of lading #, and then by date and shipper name, etc,
Next they will want to archive more documents then just invoices, along with
a host of other retrieval paths.
If successful, it can expand quickly.
My suggestion: take a serious look at a package if possible.
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Mildenberger
Sent: Thursday, November 01, 2012 10:16 AM
Subject: datalink columns
We are planning on archiving a pdf copy of our invoices in the IFS. To
link these files to the customer/invoice/etc. I am going to create a
table with these values and the filename in the IFS. From my reading it
seems like a datalink column is the way to do it. I have never used
these and am going to start doing some testing. Has anyone done this
and are there any gotchas? Or, is there a better way to do this than
Davis Transport Inc.