Phantom Network Drives Created?

[Sam]

Hi, we have a simple db created in Access 2003 that is installed on PCs
running XP Pro and now Office 2007.
At times when it's installed from always the same mapped drive letter (the
db resides on a network drive) on the client
PCs several phantom drive letters appear on the target PCs. How can I stop
this from happening?

Let me know if I haven't adequately described the problem.

Sam

 

[dad and tony]

Hi, we have a simple db created in Access 2003 that is installed on PCs
running XP Pro and now Office 2007.
At times when it's installed from always the same mapped drive letter (the
db resides on a network drive) on the client
PCs several phantom drive letters appear on the target PCs. How can I
stop this from happening?

Let me know if I haven't adequately described the problem.

Sam

 

[Arvin Meyer [MVP]]

You may not have the same mapping on each PC. You really need to split your
application and run the front-end on each workstation and the datatables on
the server. That way you avoid one of the main chances of corrupting the
database. Have a look at:

Splitting the database:
http://www.granite.ab.ca/access/splitapp/overview.htm

 

[Ken & Lyndal Lane]

Hi, we have a simple db created in Access 2003 that is installed on PCs
running XP Pro and now Office 2007.
At times when it's installed from always the same mapped drive letter (the
db resides on a network drive) on the client
PCs several phantom drive letters appear on the target PCs. How can I
stop this from happening?

Let me know if I haven't adequately described the problem.

Sam

 

[Sam]

You may not have the same mapping on each PC. You really need to split
your application and run the front-end on each workstation and the
datatables on the server. That way you avoid one of the main chances of
corrupting the database. Have a look at:

Splitting the database:
http://www.granite.ab.ca/access/splitapp/overview.htm
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

The DB is on the mapped network drive.

What I'm thinking is I always map the same drive (G) to each PC but theat
drive may already be mapped to a different drive letter on the PCs.

Sam

 

[Sam]

This is an OS issue. If you're using Windows XP, Open My Computer or file
explorer, Folder Options - click the View tab - Advanced settings - Files
and
folders - uncheck Automatically search for network folders and printers.

If it's possible to avoid using mapped drive, do so. So far, is your
mapped
drives stable? Any disconnection?

Those aren't phantom drives, these are shared drive on users PC.

Sam wrote:

I'll uncheck the Search for Network Drives.

However, the appliction short I'm installing on some PCs is replicated three
or more times.
The original question.

 

[John W. Vinson]

What I'm thinking is I always map the same drive (G) to each PC but theat
drive may already be mapped to a different drive letter on the PCs.

That's one of many good reasons to use the unambiguous \\server\path\filename
linking rather than (changable) mapped drive letters.

 

[Arvin Meyer [MVP]]

The DB is on the mapped network drive.

What I'm thinking is I always map the same drive (G) to each PC but theat
drive may already be mapped to a different drive letter on the PCs.

Users should not be typically mapping drives to the network though. A login
script that maps the drives is also a good solution. Or as John mentioned
use a Universal Naming Convention. In any case, you still MUST split the
application to avoid both corruption and unnecessary network traffic.