Error 3044 'Z:\xxxxxxx.mdb' is not a valid path

  • Thread starter Thread starter croy
  • Start date Start date
C

croy

A form that does some importing and appending has worked
great for several years. But after returning from a
vacation, the form now throws an error:

"3044 'Z:\xxxxxxx.mdb' is not a valid path. Make sure...."

I've searched thru the mdb looking for any instance of
"Z:\", but found nothing.

All the linked tables are on W:\.

What could be causing this?
 
Did someone perhaps use the database while you were on vacation and relink
one or more tables to something on the Z: drive?

"croy" wrote in message
A form that does some importing and appending has worked
great for several years. But after returning from a
vacation, the form now throws an error:

"3044 'Z:\xxxxxxx.mdb' is not a valid path. Make sure...."

I've searched thru the mdb looking for any instance of
"Z:\", but found nothing.

All the linked tables are on W:\.

What could be causing this?
 
Did someone perhaps use the database while you were on vacation and relink
one or more tables to something on the Z: drive?
Click to expand...

Thanks for the look.

Someone did use the computer, but there's no mapping to a
"Z:" drive on this computer.

I've refreshed all the table links several times with no
problems, and they all point to the mapped "W:" drive (where
they should, and always had).

I was able crudely fix the problem by blowing away the form
and importing it from a backup made before my vacation. But
I have no idea why that fixed the problem. I did a
side-by-side compare of the before and after forms' code,
and couldn't find anything different.
 
Mappings are not usually computer-specific: they're more commonly be
user-specific. Plus any user can map any drive to a different location...

That's one of potential problems with using mapped drivers when linking to
back-end databases. If you use a UNC (\\server\share) instead, you won't
have this issue.

"croy" wrote in message
Did someone perhaps use the database while you were on vacation and relink
one or more tables to something on the Z: drive?
Click to expand...

Thanks for the look.

Someone did use the computer, but there's no mapping to a
"Z:" drive on this computer.

I've refreshed all the table links several times with no
problems, and they all point to the mapped "W:" drive (where
they should, and always had).

I was able crudely fix the problem by blowing away the form
and importing it from a backup made before my vacation. But
I have no idea why that fixed the problem. I did a
side-by-side compare of the before and after forms' code,
and couldn't find anything different.
 
Mappings are not usually computer-specific: they're more commonly
be user-specific. Plus any user can map any drive to a different
location...

That's one of potential problems with using mapped drivers when
linking to back-end databases. If you use a UNC (\\server\share)
instead, you won't have this issue.
Click to expand...

And a UNC mapping is no slower, as all mapped drive letters are
resolved to the UNC path, in any case.

I have considered mapped drive letters a complete waste of time for
nearly 15 years and don't use them at all.
 
Back
Top