Fwd: RE: [AccessD] linked table trouble

pedro at plex.nl pedro at plex.nl
Fri Feb 4 09:19:27 CST 2005


Hello Jim,

this explains a lott.
The link in access is made with mapped drive, but the actual connection with the network is made by UCN. But still with UCN in WindowsXP, when making a connection you fill in a letter and then make the connection by UCN.

Maybe the best way is to reconnect each startup by code, But i don't know how this code is made.

Nice to now that after al these years i learn that connecting  in a way like \\Server_a\data is called UNC


Pedro Janssen



From: Jim Lawrence <accessd at shaw.ca>
To: "'Access Developers discussion and problem solving'"
Date: Thu, 03 Feb 2005 18:48:13 -0800
Subject: RE: [AccessD] linked table trouble


Hi Pedro:

Mapped drive connections would be something like:
H:\apps\MyApplications\MyAccess.mdb

And UNC would be something like:
\\MySecondServer\apps\MyApplications\MyAccess.mdb

The second way can sometimes be better as a user at their station could
select another letter for their network drive.

HTH
Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Pedro Janssen
Sent: Thursday, February 03, 2005 1:22 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] linked table trouble

Hello All,

the troubles are in A2K3 format databases.

About the UNC or mapped drive connections.
Maybe due to differences in our language i do not really understand what you
mean. The database i am using is not a real backend or frontend database. It
uses just one table from another database in witch we store the data of our
hospital specialists. Both databases are in different folders on a file
server, on which we login to.

Bobby could you provide me the code for the programmatically relink.

Thanks to all

Pedro



----- Original Message -----
From: "Charlotte Foust" <cfoust at infostatsystems.com>
To: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
Sent: Thursday, February 03, 2005 9:23 PM
Subject: RE: [AccessD] linked table trouble


> The complaints I've heard about have been in all file formats.
>
> Charlotte Foust
>
>
> -----Original Message-----
> From: Jim DeMarco [mailto:Jdemarco at hudsonhealthplan.org]
> Sent: Thursday, February 03, 2005 11:58 AM
> To: Access Developers discussion and problem solving
> Subject: RE: [AccessD] linked table trouble
>
>
> Pedro and/or Charlotte,
>
> Is this with A2K3 format databases, A2K format, or both?
>
> TIA,
>
> Jim DeMarco
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte
> Foust
> Sent: Thursday, February 03, 2005 2:39 PM
> To: Access Developers discussion and problem solving
> Subject: RE: [AccessD] linked table trouble
>
>
> I don't have an answer for you, but I've heard that complaint several
> times in other forums too.
>
> Charlotte Foust
>
>
> -----Original Message-----
> From: Pedro Janssen [mailto:pedro at plex.nl]
> Sent: Thursday, February 03, 2005 11:08 AM
> To: AccessD at databaseadvisors.com
> Subject: [AccessD] linked table trouble
>
>
> Hello Group,
>
> in the past we never had any troubles with linked tables.
> Since whe are using A2003 the link between the databases and tables must
> be renewed (with the linked Tabel manager) very often, in some computers
> each morning. How is this possible? Is there a solution?
>
> Pedro Janssen
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>
>
>
>
>
> ************************************************************************
> ***********
> "This electronic message is intended to be for the use only of the named
> recipient, and may contain information from Hudson Health Plan (HHP)
> that is confidential or privileged.  If you are not the intended
> recipient, you are hereby notified that any disclosure, copying,
> distribution or use of the contents of this message is strictly
> prohibited.  If you have received this message in error or are not the
> named recipient, please notify us immediately, either by contacting the
> sender at the electronic mail address noted above or calling HHP at
> (914) 631-1611. If you are not the intended recipient, please do not
> forward this email to anyone, and delete and destroy all copies of this
> message.  Thank You".
> ************************************************************************
> ***********
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com





More information about the AccessD mailing list