Why does it need to be object based? A good image viewing program won't care what the file extension is and interrogate the file header to determine what type of file it is.
If anything is the blame here its content manager for completely bastardizing the files, storing overlays in an undocumented format, and only allowing 8 meta data fields to fill in data into!
From: CRPence [mailto:CRPbottle@xxxxxxxxx]
Sent: Tuesday, February 26, 2013 2:34 PM
Subject: Re: view ifs image and specify viewer with strpccmd
Ah. So having suggested the name is "like B01291AA.BID" is even more variable that I had inferred from the description. Ah well. If the PC OS was object-based, it would be moot. Such a strange concept that a file extension should define the /type/ of object :-(
So I guess double-clicking the file name, even on the PCs with the CM client installed will have no idea what to do with the .BID file? And the only way to deal with the managed content is via the view provided by the CM client.?
On 26 Feb 2013 12:05, Matt Olson wrote:
This poor soul is using content manager, a tiff file can be named--
.BID, .A26, .B9L, and any other combination of three letter / number
combinations. He would have to register all 7,140 permutations (if I
did my math correctly) on every PC in the network! Ouch!
CRPence Tuesday, February 26, 2013 2:01 PM
On 26 Feb 2013 08:33, J Franz wrote:
However we have an issue where the doc name is "non-standard"
like B01291AA.BID (this is IBM Content Manager stuff) and need to
tell the browser what viewer to use (it's tif or pdf) and need to
view on a PC with no Content Manager client.
The file-extension 'bid' can be /registered/ to be associated with a
TIF viewer <<SNIP>>
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact