Off97 to O2K Hyperlink Woes…. (O2K)

Topic

New Reply

We have our policies online. Users have read-only access to an index which contains a hyperlink that directs them to the read-only policy.

For those users who have Office 97, their hyperlink ‘bubble’ reflects the full UNC to the policy document and it launches correctly.

For those who have Office 2000, their hyperlink ‘bubble’ reflects ….directoryfilename and the link results in the following error:

The address of this site is not valid. Check the address and try again

Interestingly, if I select Update Field on the hyperlink for a Office 2000 user, the link will update and reflect the full UNC name and, therefore, will launch. But this is only a bandaid fix as the users cannot SAVE the file for this correction to stick.

Any ideas?

Reply | Quote

Replies

Sorry, but I don’t know what a hyperlink ‘bubble’ is. Where in Office are you doing this, in one of the applications, the shortcut bar or where?

Reply | Quote

The link was created in a Word document. It links to other Word Documents
Hyperlink bubble = the link that appears when you hover your cursor over the link

Out of three PCs not functioning, I actually got one to work by doing the following (although I’m not sure which actually corrected the problem):

1. Upgraded Novell Client to 3.3
2. Ran Detect & Repair in Word
3. RegSvr32 Hlinkprx.dll (based on a tech note I found which was semi-sort of related)
4. Noted that no Service Packs have been applied

Curiously through, I took these same steps on one of the other PCs and it did not resolve problem I did try loading up to SP2 on one, malfunctioning PC, but this also did not resolve.

Reply | Quote

Hyperlink ScreenTip (the proper name for

Reply | Quote

[indent]

---

Interestingly, if I select Update Field on the hyperlink for a Office 2000 user, the link will update and reflect the full UNC name and, therefore, will launch. But this is only a bandaid fix as the users cannot SAVE the file for this correction to stick.

---

[/indent]This might be a difference between Office 97 and Office 2000 that was added to aid in web authoring, but which is less helpful in a file server environment.

Is there any reason you could not update the links in 2000 and save over your original to resolve the issue for everyone? Would that create problems for the 97 users?

Alternately, you could add an AutoOpen macro (or Document_Open event procedure) to refresh all the fields when the users open the document. Then, even though it is a band-aid, it is a self-applied band-aid and the users won’t have to go through the click-oops-refresh-click again cycle. The downside, of course, is that you might have different levels of macro security in effect and thus some users might get security prompts while for others it might not run at all.

Reply | Quote

I have actually found a work-around. All users H: drives are mapped to servernamevolusers, which then gives them access to their own directory, as well as these online ‘public’ directories. On several machines, however, the link was not working. The commonality between these machines seemed to be Office 2000.

I mapped another drive to P: using servernamevolusersadmin policies (the actual directory containing the document with the linked indexes). Well, it was no surprise that this mapping solved the problem. HOWEVER, when I look at how the drives actually map, it was curious that they both mapped as follows: servernamevolusers. The end result is that P: works and H: does not….

I thought I understood Novell mapping, but it continues to elude me….

Reply | Quote