K
Kathy
I have a split database on Windows 2003 Server that clients access through TS
and RDC. Each client logs on the server to their front end database. Some
clients require access to other client backends. I have the link table
procedure automated so the client navigates to the backend folder, chooses
the backend they want at the time and all the tables are linked. They do not
have the option to choose which tables they link to within that database nor
can they choose some tables from one database and some tables from another.
In the front end I have added a cmd button to open an additional database,
this option needs to open a different database for each client. This
database is a platform allowing clients to create hyperlinks to addition
photos and files located in a folder. When I first designed the hyperlink
form I put the related table in each client backend, when they linked to a
backend the appropriate hyperlink data was visible. I have experienced a
problem when a client adds a hyperlink from their "location", the hyperlink
opens the appropriate document. When another client links to that backend,
the hyperlinks no longer work because they are calling the doc from a
differnet location.
I want to create a separate "hyperlink db" for each client that they can
open from within the first dabase. But when i deploy the front end to each
client the cmd button will open only the one hyperlink db. I used a run
application macro connected to a cmd button but I don't want to have to
modify the macro each time I updated and deploy a front end.
Can someone help me with the code needed so that when the front end is
linked to a particular backend the path in the run application procedure can
find/change to the matching hyperlink db?
and RDC. Each client logs on the server to their front end database. Some
clients require access to other client backends. I have the link table
procedure automated so the client navigates to the backend folder, chooses
the backend they want at the time and all the tables are linked. They do not
have the option to choose which tables they link to within that database nor
can they choose some tables from one database and some tables from another.
In the front end I have added a cmd button to open an additional database,
this option needs to open a different database for each client. This
database is a platform allowing clients to create hyperlinks to addition
photos and files located in a folder. When I first designed the hyperlink
form I put the related table in each client backend, when they linked to a
backend the appropriate hyperlink data was visible. I have experienced a
problem when a client adds a hyperlink from their "location", the hyperlink
opens the appropriate document. When another client links to that backend,
the hyperlinks no longer work because they are calling the doc from a
differnet location.
I want to create a separate "hyperlink db" for each client that they can
open from within the first dabase. But when i deploy the front end to each
client the cmd button will open only the one hyperlink db. I used a run
application macro connected to a cmd button but I don't want to have to
modify the macro each time I updated and deploy a front end.
Can someone help me with the code needed so that when the front end is
linked to a particular backend the path in the run application procedure can
find/change to the matching hyperlink db?