Chekov
Active Member
Hello everyone
I have a general question on the general use of Media objects in E1. Our users want to make use of the row attachments for storing scanned docs and in particular supplier invoices (media object GT0411). Management want to avoid the expense of an external 3rd party solution if possible so we are looking to a workable internal solution with current infrastructure
I have estimated there are some 250k records per annum in total to be stored. In P98MOQUE we map the object queues to a data file share (windows 2003).
The average file size (PDF or TIF) seems to be between 50-100kb per file though for some strange reason when PDF is stored as an embedded OLE object this leaps to >2Mb per file (TIF file remains much the same size)
Does anyone have experience of extensive use of Media objects and can offer some helpful advice on linking vs embedding and on an approach to manageable file storage structures? Does the number of records seem excessive?
Any help would be appreciated, thanks
Al
I have a general question on the general use of Media objects in E1. Our users want to make use of the row attachments for storing scanned docs and in particular supplier invoices (media object GT0411). Management want to avoid the expense of an external 3rd party solution if possible so we are looking to a workable internal solution with current infrastructure
I have estimated there are some 250k records per annum in total to be stored. In P98MOQUE we map the object queues to a data file share (windows 2003).
The average file size (PDF or TIF) seems to be between 50-100kb per file though for some strange reason when PDF is stored as an embedded OLE object this leaps to >2Mb per file (TIF file remains much the same size)
Does anyone have experience of extensive use of Media objects and can offer some helpful advice on linking vs embedding and on an approach to manageable file storage structures? Does the number of records seem excessive?
Any help would be appreciated, thanks
Al