By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,098 Members | 989 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,098 IT Pros & Developers. It's quick & easy.

Link Table Manager path problems

P: n/a
I wrote a C# asp.net app. that uses MS Access as a backend. I forgot
include in my design that the Link tables would break when I deployed
the application to the "Live" server.

The problem is: I can connect to the share on the "live" server but the
person who will periodically update the Database cant --he has to use a
SSH Secure File Transfer Client. So I can change the path in the "Link
Table Manager" to "\\Newserver\NewShare\etc.." but he cant.

Is there a way to fool the "link Table Manager" to except a path that
doesn't exit on the old server but will on the "Live" server?
Thanks
--Dietrich

Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
On 31 Jan 2005 15:09:53 -0800, "dw******@uiuc.edu" <dw******@uiuc.edu>
wrote:
I wrote a C# asp.net app. that uses MS Access as a backend. I forgot
include in my design that the Link tables would break when I deployed
the application to the "Live" server.

The problem is: I can connect to the share on the "live" server but the
person who will periodically update the Database cant --he has to use a
SSH Secure File Transfer Client. So I can change the path in the "Link
Table Manager" to "\\Newserver\NewShare\etc.." but he cant.

Is there a way to fool the "link Table Manager" to except a path that
doesn't exit on the old server but will on the "Live" server?
Thanks
--Dietrich

Hi
There may be, but can't you set up so that the same path exists in
your deveopment system and on the target system? You will probably
have to use mapped drives on one or both systems.
But, as mentioned earlier in the group by Stephen K Young, the
following article:

http://support.microsoft.com/kb/889588

"How to optimize Office Access and Jet database engine network
performance
with Windows 2000-based and Windows XP-based clients"

includes the recommendation to use mapped drives instead of unc paths

David
Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.