Windows/Excel security warning on internal link location?

[#1]

Probably very common, but don't know how to get rid of the warning box that pops up every time a link is placed in an Excel cell.
The location of the linked file is currently C:Documents of the local machine.
This Excel file will eventually need to be accessed by others on a small network.
The warning is along the lines of an "unsafe location".
Doesn't seem to be a 'don't ask again' option.
Not sure if its a Windows thing or just Excel. My guess is Windows.
Got a feeling I'll probably have to find whoever set up the network, but maybe there's a quicker solution?
Don't pretend to understand anything about networks in this respect!  
 edit - this is v small LAN in office, 3 computers only.
This link gives registry change info -
http://support.microsoft.com/kb/925757
but even so, not sure how this works on a network? Fix every computer?

[#2]

This is more likely to be an Office/Excel issue. Which version are you using?

[#3]

Think you're right.
Its 2007.
Can't do anymore about it till Monday.
Might have to try that registry fix - but seems a bit wild just to stop a warning box (esp as it refers to a file on C:Documents!)
Folks in office wont be too happy about that probably...

[#4]

Almost certainly Microsoft!.  IIRC it was Ofice 2007 that introduced additional constraints on files accessed via URL.  2010 took it a lot further
The good news is that you can modify the settings (at your risk) via Files / options / Trust Centre.  In 2007 I think it was either 'Connection file location or 'Trusted Locations'.
Even better is that with Windows 7 or Server 2012 systems you could use Group Policy to manage and control this (and many others feature) more securely.  IMO well worth investing some time and effort on Group Policy to assist in keeping common things like Fonts, paper sizes etc in line as well as the security options.
Maurice

[#5]

Quote from: IanSn

Might have to try that registry fix - but seems a bit wild just to stop a warning box (esp as it refers to a file on C:Documents!)

It maybe a long way for a short cut but you have to remember that that C:\ drive may not even be yours, and with Office's ability to execute code its there to protect you so I think you should proceed with caution. I know it's tedious but you may live to regret it.

[#6]

@Mook
Yes, indeed.
Was thinking something like that.
I guess C: is actually networked. Therefore...
Doubtful folks in this office will be happy with registry edits anyway.
Will try in OpenOffice. If is ok, does that mean OO is a security risk or that it doesn't execute code in the same way?

[#7]

Open Office is an option but VBA code won't run on it, but it does have a scripting language of its own. I used to use OO but had to ditch it in favor of Excel due to the issue of not running code, macros etc.

[#8]

They have LibreOffice installed at the office I'm in at the mo. Could try that. Don't need macros for this job, but do have drop-downs which, in Libre here at home, is giving #NAME? errors (not in Excel). OpenOffice is giving Err: 509 in the same places.
Ha! Need to figure out why that is.
But they probably don't want to move from Excel anyway.
I'm guessing we'll have to put up with the 'unsafe location' box.
Just doesn't look good when clients want to see pic of item and get a warning everytime....

[#9]

@MauriceC
Sorry, missed your comments before.
Thanks, I'll look into that on Monday. Could be the answer.

[#10]

I'd go with MauriceC's suggestion first.

[#11]

Yes, will do.
Odd that on the Microsoft site there was no mention of this to any of the many queries on the same/similar topic!

[#12]

Didn't have time today to delve into this, but looks like me and folks are going to have to get heads round 'Group Policy', none of us having done so before.
Will post results if anyone interested in all this.