Microsoft access run time error 3044 (1 Viewer)

Ace Brendon · Jun 17, 2017

I am getting a runtime error while starting my database file as follows:

MICROSOFT ACCESS RUN TIME ERROR 3044

C:\Hayes Server\Data\yes4\yeshaeya.mdb is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server onto which the file resides.

I get an option to debug, end and cancel.

If I use debug--> Opens VBA which I have no idea.

End will close the database file and cancel will also do the same...

This file, however, opens good on other systems which are also Windows XP and have office 97 Pro installed.

This system too has Windows XP and has Office 97....

It used to open good earlier however now since two weeks it is not working good....

Have tried to delete the file from this system copy it from other system and then try to run.... Still no go...

Have tried to create new user account... Still same issue...

NOTE: THE FILE EXISTS ONTO THE C: ITSELF AND NOT ON Z: As the error states

Any help would be greatly appreciated.

Ranman256 · Jun 17, 2017

you should have opened in vba, captured a screen shot, and posted it,
but
IS that a valid path?
when does it happen, when you open the db?, when you click something while open?
is this path hardcoded into a form or used in code?

Ace Brendon · Jun 19, 2017

Hi Ranman,

I will do it now....

Sorry for that....

Will post the error in next reply....

Thanks....

Ace Brendon · Jun 19, 2017

Here is the screenshot of the same...

The error happens when I try to open the Access database....

The file opens good on other two systems but unfortunately not on mine...

It is in the zip file as the size was exceeding the limit...

Also, i am attaching the VBA code as well however we haven't used any VBA script as well...

CJ_London · Jun 19, 2017

the reference to the z drive is not made up by access, it will be there in your code or perhaps you have linked tables to a file on a z drive.

Ace Brendon · Jun 20, 2017

As I mentioned earlier that we do not use any coding and it just a database file.....

For the very same reason have attached both the error code and the VBA script as well.....

So if you can please go through it and then let me know....

I would not be able to check the linking of the table as the file does not load itself.....

I get this message the moment I try to open the database file.....

jdraw · Jun 20, 2017

I agree with what CJ said. The reference to Z must be somewhere in code or set up procedures or a previous link or ???, but Access doesn't just make up drive letters.

What happened 2 weeks ago when things no longer worked as expected??

CJ_London · Jun 20, 2017

Code:

So if you can please go through it and then let me know....

No because -

1. you say you don't use any coding, but attach a screenshot of some.
2. I cannot check linked files only you can
3. the error screenshot does not match the text in your post

if it works on other machines, but not yours, it has to be to do with the setup of your machine.

CJ_London · Jun 20, 2017

I get this message the moment I try to open the database file.....

try holding down the shift key whilst opening the db

Ace Brendon · Jun 20, 2017

Hi Please find the file attached when i try to open the database file while holding down the shift key....

Also In reply to the below queries are my responses:

1. you say you don't use any coding, but attach a screenshot of some.

This VBA comes up when i press debug if i press end....

2. I cannot check linked files only you can.....

If you can guide me how to check the linked file that would be great.....

3. the error screenshot does not match the text in your post

the first screenshot in the zipped format is the error I get and the second zipped file is the VBA that opens up when i click debug....

CJ_London · Jun 20, 2017

If you can guide me how to check the linked file that would be great.....

see post #9

Ace Brendon · Jun 20, 2017

yes i followed that step and that is what is the screenshot i have attached....

CJ_London · Jun 20, 2017

holding down the shift key prevent the vba code from running. So perhaps it has been disabled.

Next choice is to open a new blank copy of the db and import the tables from the one you can't use. You can then see if they are linked and if so, what they are linked to - my gues would be to a database on a z drive

Ace Brendon · Jun 20, 2017

Ok I was in the process of importing the tables when i got this message that :

Z:\hayess~1\Data\Yes4\yeshayea.mdb is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server onto which the file resides...

I hit Ok 3 -4 times and then it gave me two names:

yescalendaricons
yescalendaricons1

CJ_London · Jun 20, 2017

well that is telling you that the table is linked to one in a z drive you don't have. You either need to map the relevant drive to z (go look at your colleagues setup) or find a way to open the database without triggering the code.

One other thing to try to do this. In your first post you said

I get an option to debug, end and cancel.

If I use debug--> Opens VBA which I have no idea.

1. choose debug and see the code
2. from the menus at the top, choose run, then reset

it might leave you with the code stopped and you have access to the database.

Ace Brendon · Jun 20, 2017

When i hit Debug this is the line that is highlighted....

Set Pref = CurDB.OpenRecordset("Preferences", DB_OPEN_DYNASET)....

If you can let me know what do i need to do at this point of time....

I checked the code on the other two systems and they both say the same coding....

NauticalGent · Jun 20, 2017

Ciao Ace,

As CJL has said, the problem lies with virtual drive assignment. I had a similar problem a couple of years ago and Ranman256 help me sort it out.

Give this thread a read:

https://access-programmers.co.uk/forums/showthread.php?t=285318

The answer is using UNC's instead of virtual drive letters, in your case drive "Z"

The_Doc_Man · Jun 20, 2017

I answered your other post.

Get into Database Tools >> Linked Table Manager and see the path associated with the tables used in your queries that have the problem. Odds are that they are linked through a Z drive. The table definitions used by the Linked Table Manager are persistent, so if you ever used Z: as a drive letter and never changed it back, that is your problem.

Ace Brendon · Jun 20, 2017

Dear Nauticle,

Thanks for your reply, however I would like to let you know that this is Access 97 and that I am not getting the option of Database Tools over here....

If i use the Shift key and then try to open it opens all the tables but it does not have the option to show me the databse tools / utilities

:banghead::banghead::banghead:

Under the database utilities I just have the following options:

1. Compact Database
2. Repair Database.
3. Make MDE File.

JHB · Jun 20, 2017

Ace Brendon said:
When i hit Debug this is the line that is highlighted....

Set Pref = CurDB.OpenRecordset("Preferences", DB_OPEN_DYNASET)....
..

What happen if you change it to:

Code:

Set Pref = CurDB.OpenRecordset("Preferences", dbOpenDynaset)

Have you checked the Library References?
http://allenbrowne.com/ser-38.html

Microsoft access run time error 3044 (1 Viewer)

Registered User.

Well-known member

Registered User.

Registered User.

Attachments

Super Moderator

Registered User.

Super Moderator

Super Moderator

Super Moderator

Registered User.

Attachments

Super Moderator

Registered User.

Super Moderator

Registered User.

Super Moderator

Registered User.

Ignore List Poster Boy

Immoderate Moderator

Registered User.

Have been here a while

Similar threads

Users who are viewing this thread