Replicated database and whirring A: Drive

[JH]

Folks,

I have been working with replicated databases and everytime I open a table
my PC insists on searching on my A: drive first. I have to put a disk in
otherwise it takes a very long time before it gives up. Any clues how to
stop this? Curiously the same db on an other machine does not have the saem
effect, I can't see what is set differently but clearly something is.

Thanks,

John

 

[John Ortt]

The only thing I can think of is that the A: drive (floppy) might be
incorrectly mapped on your machine (For example as D.

If there is a linked table on a D: drive it would couse your computer to
search for this table unsuccessfully on D:.

I could be wrong but this is all I can think of if your computer is the only
one doing it...

Hope this is of some help,

John O

 

[Joan Wild]

I have been working with replicated databases and everytime I open a
table my PC insists on searching on my A: drive first. I have to put
a disk in otherwise it takes a very long time before it gives up. Any
clues how to stop this? Curiously the same db on an other machine
does not have the saem effect, I can't see what is set differently
but clearly something is.

Use Windows Explorer to check whether the A: drive is shared. It shouldn't
be.

 

[Mike Labosh]

I have been working with replicated databases and everytime I open a table

my PC insists on searching on my A: drive first. I have to put a disk in
otherwise it takes a very long time before it gives up. Any clues how to
stop this? Curiously the same db on an other machine does not have the
saem effect, I can't see what is set differently but clearly something is.

I'll add this one...Check the property dialog for the shortcut you use to
launch Access or your application, and look at the "Working Folder" entry.

 

[JH]

Thanks Joan, this was the answer!

Thanks to the rest of you that replied,

JOhn