• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 78
  • Last Modified:

Runtime 3044 error

Error messageI am trying to access the file which is M: drive ( network drive ) its access data base file.

When i try to open it, its giving me error with w: and the error it cannot be specified
Even i dont have w: in my computer
0
Kunal mahajan
Asked:
Kunal mahajan
  • 7
  • 4
  • 2
  • +1
1 Solution
 
pcelbaCommented:
You have to ask the database application author why he uses hardcoded W: drive letter.
0
 
Kunal mahajanAuthor Commented:
Thanks for the answer, it means the file which is in error message , its in W drive on which i dont have the access becuase there is no W drive on my computer
0
 
Kunal mahajanAuthor Commented:
My others colleges can access this file, with no issue only me ! I checked even wheather i do have permissions, m good with it
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
pcelbaCommented:
This is standard situation in many companies. Some people do have access to certain files/drives others don't... Drives are mapped automatically during the login.

You may try to map the W: drive yourself if you know the network name and path. Or better, you may ask your network administrator to do it for you. It should be one minute task for him.
0
 
Kunal mahajanAuthor Commented:
But we hve given the instruction the file is in M drive: where I go and try to access this file and when i am accessing this getting error with W: error message.
I will show you the access to my drives
IMG_4024.JPG
0
 
Jason clarkDBA FreelancerCommented:
Not necessarily; if the paths is change then that could be modified. You could rebuild your system and make the system drive 'm' again.
0
 
John TsioumprisSoftware & Systems EngineerCommented:
This is a split Access so from M you are accessing the front End and the data files (Back End) is on W...the easiest way to work this is to make a map to W...just go the path described by on the 1st screen shot and make a network drive....
w.jpg
0
 
Kunal mahajanAuthor Commented:
Thank you so much, I tried doing that i wont let me map says windows cannot diognose it when i am trying to map
Network drive with same path as screen shot error
0
 
John TsioumprisSoftware & Systems EngineerCommented:
Then probably you have a different error like permission issue....
TAKE special note that the path is a path so the .accdb is not included....I cannot see very clear from the screenshot but it is :
\\TheServerName (? ... ADMINISTRATIVE )\...\Central Recors Room\
don't try to set it by hand...browse to find it...if it maps...everything OK...if not you don't have access.....or your server has stuck and needs a reboot...
0
 
Kunal mahajanAuthor Commented:
I can acccess this path through M drive from where i am trying to access the front end, intried to map it and gave letter W to it and still the error is same
0
 
pcelbaCommented:
Could you show in e.g. Windows Explorer how did you map the W: drive and that the file is available?
Did you ask the application author?
0
 
Kunal mahajanAuthor Commented:
Thanks guys, the ussur has been resolved i was using wrong path for W drive . Thanks for your replies appreciate it
0
 
pcelbaCommented:
Great!

So it seems the problem is resolved and you could close the question. At least three answers were pointing you to the W: drive mapping. :-)
0
 
Kunal mahajanAuthor Commented:
Tha ks. For your help
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 7
  • 4
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now