I have a report I've written for a client that contains a linked OLE object(ms Word doc). When the client runs the report, it does not reflect any changes to the word doc since the last Crystal modification.
The client stores the word doc on a mapped drive, such that the path is G:\xxx.rtf. While I have that exact path mapped on my pc, the OLE source within the Crystal Report shows as \\192.999.10.10\xxx.rtf, using the hardware address in lieu of the G:I suspect that this mapped drive vs hardware address is the cause of my problem as the linked object functions correctly when the report is modified to use C:\Temp as the Linked OLE Object Source location.
Has anybody seen anything like this before? Is this(mapped drive vs hardware address) a setting that can be changed? I suppose it could be an issue with my network configuration, can anybody confirm what the OLE linked object source looks like on their pc when linked to a mapped drive?
Thanks in advance for any help.
Jeff
The client stores the word doc on a mapped drive, such that the path is G:\xxx.rtf. While I have that exact path mapped on my pc, the OLE source within the Crystal Report shows as \\192.999.10.10\xxx.rtf, using the hardware address in lieu of the G:I suspect that this mapped drive vs hardware address is the cause of my problem as the linked object functions correctly when the report is modified to use C:\Temp as the Linked OLE Object Source location.
Has anybody seen anything like this before? Is this(mapped drive vs hardware address) a setting that can be changed? I suppose it could be an issue with my network configuration, can anybody confirm what the OLE linked object source looks like on their pc when linked to a mapped drive?
Thanks in advance for any help.
Jeff