On 03/27/2014 07:49 AM, Alan Bourke wrote: > This functionality is something I've never used over the years. A good idea. Object Linking and Embedding was great for demos, but problem-filled for production systems.
> The customer has now moved the images in question to an identical > directory structure on another server and/or drive, and re-mapped drive > G: to the new share, so that the apparent path to each image is > identical in terms of Windows. However these General fields seem to have > information about the original location embedded somewhere, and the link > is somehow broken. How, somehow? Is there a somehow error message? A somehow lack of image? A somehow C5 or 1429 error? Is there somehow code that shows how the somehow broken is, er, broken? > Is this a feature of General-type fields and OLE data? Is there any > simple way of re-linking ? One of many problems with OLE is that it stores a blob (structured binary data) based on the original image/document, and also the application that stored it into the field, so if you were storing a BMP that's associated with MSPaint, MSPaint would be responsible for storing the data. If you had PaintShopPro on your machine, and associated JPGs with that, it would be PSP that was responsible for storing (and retrieving) the blob of data. I think the GUIDs of the associated executable were also embedded in the blob, along with a bitmap representation and the data. So, one way to try to reproduce this is to recreate one of the original workstations and the software used to store the data. However, since you LINK rather than EMBED, you have the images available outside the app (Whew, that's usually the big concern). So the question is how to link from free image to record. I guess it depends on the answers to the "somehow" questions above. If you're getting a 1429 error with a SYS(18) of "Can't find file G:\something\image.jpg" you could do a TRY...CATCH to get the error message and re-link (using a text link to filenames and/or paths) and discontinue use of the General field. With more info, perhaps we can supply more suggestions. (Author of "OLE is No Bull" introducing Object Linking and Embedding in FoxPro Advisor. The headline was not my fault, nor my opinion.) -- Ted Roche & Associates, LLC http://www.tedroche.com/ _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
