Runtime Error 3044

Most likely a path changed, a drive lost it's mapping, etc. When the error pops up hit debug and the offending line of code will be highlighted.

I dont have the option to hit debug...how do I do that?

where do you see the error message, are there no debug or end buttons?

This is a VB executable?

no...I get the error when I click on the .exe file to run the program.

Do you know the location of the database and has it moved? I've seen this when a drive loses mapping to a UNC path.

By the way, welcome to EE.

Here is a screenshot of the error that I am getting.  It used to work on my other computer and my hard drive was a c: drive now it is an e: drive....I wonder if that is the problem.

Yes the database is in the same folder as the program.  Thanks for the welcome...I cant believe I am getting responses this fast.  I have been trying to fix this problem on my own for the last 3 days...and searching all over the net but havent had any luck.
ScreenHunter-02-Jan.-30-21.23.gif

That is the problem, change back to C witrh the same folder structure and everything should be OK again.

How do I change the E: drive to have the name C:.  I have a Sony Laptop and it defaulted the hard drive to the name E: and one of the other usb drives is named C:

I'll bet that the path is hard coded into the program, and if it is then you can't change it. If you have Microsoft Access installed you could check the tables to see if one has the paths stored there otherwise it looks like the db goes ion the usb drive

The path is a variable that is currently a null-string.  The coded routine before the variable is being put to use as a path is important.  It needs to be showing here.

with the error on screen hit
[CTRL] [BREAK] and see which line is causing the problem.
post the relevant parts of the routine here

I hit ctrl break when the error was on the screen and it closed the program.  Do I need to be in a certain program when I hit control break?

is the program in the form of an Access MDE file at runtime?

It's a VB.exe

jadedata,

milton doesn't have anything but a compiled .exe. The problem is that the access database for the vb app was mapped to the c drive and now the c drive is a thumb drive.

Regards,

Jim

Guys thanks for the help...I got it fixed...  The configuration file was wrong...it was set to systemdb=c:\windows\pfbp.mda and I changed it to systemdb=e:\pfbp.mda and it WORKED...

Thanks again for the help.

~Milton