E
Eric
Hi,
I have asked this question to the access newsgroup to no
avail, so I'll try it here. I built a networked access
2000 db at the company I work for. Most machines have 2
versions of access installed on them - 97 and 2000, some
have only 2000. The problem is that the access 2k
executable is located in different folder locations from
machine to machine - ie Office v Office1 v Office2000.
Due to the discrepancy, the custom link I created to open
the database keeps getting confused from machine to
machine. I know there must be a way to make a .lnk with a
directory that is not hard-coded. For instance in both
the "Target" and "Start In" command lines. How can I
script the link to find the location of access 2000 from
computer to computer? It has been suggested I purchase
third party software to accomplish that, but that isn't
feasible. Any input would be creatly appreciated. Thanks,
Eric
I have asked this question to the access newsgroup to no
avail, so I'll try it here. I built a networked access
2000 db at the company I work for. Most machines have 2
versions of access installed on them - 97 and 2000, some
have only 2000. The problem is that the access 2k
executable is located in different folder locations from
machine to machine - ie Office v Office1 v Office2000.
Due to the discrepancy, the custom link I created to open
the database keeps getting confused from machine to
machine. I know there must be a way to make a .lnk with a
directory that is not hard-coded. For instance in both
the "Target" and "Start In" command lines. How can I
script the link to find the location of access 2000 from
computer to computer? It has been suggested I purchase
third party software to accomplish that, but that isn't
feasible. Any input would be creatly appreciated. Thanks,
Eric