B
BruceM
I am hesitant to describe something as a bug, but if this is not a bug it
seems to be at least a full-blown anomaly.
The situation occurs when I insert a hyperlink by way of:
DoCmd.RunCommand acCmdInsertHyperlink
It may be that it occurs if I insert the hyperlink by using the menu bar or
tool bar, but I couldn't say for sure.
In all situations the Add/Edit Hyperlink dialog appears as expected when I
run the code. The problem, when it occurs, comes later. ServerName is the
server, Shared is the network drive, Status Reports is the folder, and Rpt
D-07-01.doc is the file.
First situation: An unsplit database located on my local hard drive
(specifically, in a My Documents sub-folder). I add a UNC link to a file
that is located on a network drive. The address of the file (in the
Add/Edit Hyperlink dialog box) appears as it should:
\\ServerName\Shared\Status Reports\Rpt D-07-01.doc
When I open the table and look at the field I see the path just described.
If I tab into the field I see:
\\ServerName\Shared\Status Reports\Rpt
D-07-01.doc#\\ServerName\Shared\Status Reports\Rpt D-07-01.doc#
From what I can tell, this is what I should see. The link works properly.
Second situation: An unsplit database located on a network drive. I add a
UNC link to a file that is located on a network drive. The address of the
file (in the Add/Edit Hyperlink dialog box) appears as:
...\..\Shared\Status Reports\Rpt D-07-01.doc
When I open the table and look at the field I see the path just described.
If I tab into the field I see:
...\..\Shared\Status Reports\Rpt
D-07-01.doc#../../Shared/Status%20Reports/Rpt%20D-07-01.doc#
The link does not work, of course. To sum up what has happened, the server
name is missing; instead, I see ..\..\
Also, spaces are replaced with %20 in the next part of the code (between the
# signs).
Third situation: A split database with the data on a network drive and the
front end (mde file) on my local computer (in a My Documents subfolder).
Everything works as it should, the same way as described in First Situation,
above.
Fourth situation: Add a mapped drive letter link. This works in all
situtations, as far as I can tell.
I have done some searching, and have found a few posts on the subject, but
no resolution. It seems to occur with Access 2003, which is what I have.
seems to be at least a full-blown anomaly.
The situation occurs when I insert a hyperlink by way of:
DoCmd.RunCommand acCmdInsertHyperlink
It may be that it occurs if I insert the hyperlink by using the menu bar or
tool bar, but I couldn't say for sure.
In all situations the Add/Edit Hyperlink dialog appears as expected when I
run the code. The problem, when it occurs, comes later. ServerName is the
server, Shared is the network drive, Status Reports is the folder, and Rpt
D-07-01.doc is the file.
First situation: An unsplit database located on my local hard drive
(specifically, in a My Documents sub-folder). I add a UNC link to a file
that is located on a network drive. The address of the file (in the
Add/Edit Hyperlink dialog box) appears as it should:
\\ServerName\Shared\Status Reports\Rpt D-07-01.doc
When I open the table and look at the field I see the path just described.
If I tab into the field I see:
\\ServerName\Shared\Status Reports\Rpt
D-07-01.doc#\\ServerName\Shared\Status Reports\Rpt D-07-01.doc#
From what I can tell, this is what I should see. The link works properly.
Second situation: An unsplit database located on a network drive. I add a
UNC link to a file that is located on a network drive. The address of the
file (in the Add/Edit Hyperlink dialog box) appears as:
...\..\Shared\Status Reports\Rpt D-07-01.doc
When I open the table and look at the field I see the path just described.
If I tab into the field I see:
...\..\Shared\Status Reports\Rpt
D-07-01.doc#../../Shared/Status%20Reports/Rpt%20D-07-01.doc#
The link does not work, of course. To sum up what has happened, the server
name is missing; instead, I see ..\..\
Also, spaces are replaced with %20 in the next part of the code (between the
# signs).
Third situation: A split database with the data on a network drive and the
front end (mde file) on my local computer (in a My Documents subfolder).
Everything works as it should, the same way as described in First Situation,
above.
Fourth situation: Add a mapped drive letter link. This works in all
situtations, as far as I can tell.
I have done some searching, and have found a few posts on the subject, but
no resolution. It seems to occur with Access 2003, which is what I have.