You are currently viewing the VB Components section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
I am taking over a web app VB6/MS Access 2003 to clean things up.
Have never worked with MS Access.
Getting a run-time error '3044' in VB stating that the path D:.... to the DB is not correct.
I can't figure out what is pulling this error. The DB lives on C:...... Code uses CurrentDb. and no hard coded D: ref in the code. I don't have the laptop here right now can't test this but wanted to ask you guys, where could this point to D: live? I am thinking ODBC/DSN? Is that the only place? I have changed the DB point in the registry before with VB however looked there and did not see any points to D: in the reg.
Any clues as to where I can fix this error because it is a show stopper for me continuing.
Thank you so much for responding. I have never worked in Access before so don't know if i am totally off base. I am taking over previous developers code.
This is a web app to generate reports using an Access 2003 back end/vb6.
What triggers the runtime error is when I go to generate the report. Get runtime error '3044' which states : 'D:\CPF\.....'
is not a valid path.
The report is running on my C drive with the Access DB living on my C drive.
I searched the code for 'D:\' to see if the previous developer had hard coded (for some reason) the DB to the D drive. Search for that D: reference in the code came back empty.
So my question is, in Access how is the DB path determined if that path is not in the code?
Do I need to address something in OBDC/DSN
Or in the registry?
Somehow the previous developer told the app to look for the DB on the D:\ drive. I can not figure out where he did this.
This is a show stopper in that I have built the front and middle tier but really need the hook up to the DB but Access is telling me it can not find the DB on the path of 'D:\...' This is a error happens everytime I try to generate the report, thus engaging the Access DB.
How does Access decide where to look for a linked DB? It is not in the vb6 code.
Thanks for ANY assistance in the client is getting antsy
Sorry to nitpick, but your answer doesn't answer. “using an Access 2003 back end/vb6” is unclear. A VB 6 app developed in the Visual Studio environment which references an .MDB, or using the VB 6 that is within Access, using the Access environment?
You answered, “when I go to generate the report,” but the meaning of my question is the actions that “go to generate” represents. Is this in code? are you double-clicking the report in the Database Window? Or...?
If you are using VB6, and Visual Studio, what technology are you using to contact the database?
Hi Brian thank you very much for your reply. No not nitpicking at all, I have never used Access, I guess that is obvious.
I am 'using the VB 6 that is within Access, using the Access environment'
Does that clarify at all? Please ask me to clarify anything if it is unclear in that I really need some help here.
That VB is actually called VBA, not VB 6, though it is the same language...
It would save time if you answered all the questions I post. Read through the post, and answer a question, then re-read and see if there are additional Qs. (There are in this case)
You answered, “when I go to generate the report,”
but the meaning of my question is the actions that
“go to generate” represents. Is this an action
taken in code (byt the click of a button, or what-
ever)? Are you double-clicking the report in the
Database Window? Or...?
This error mcome when you link tables via mapped drive user UNC instead or lost network connection. It is quite possible that every time the database is opened, the startup deletes current links and creates new links to tables in a file path set in an ini file. to avoid this error Set dbs = Workspace.OpenDatabase (”C:\Temp\Database.mdb”)
Check for the path and file must be valid for a statement using the CurrentDB method to function properly or you can try to delete link table. It is also possible to change or examine the connect property of a table. If still get error that means your database is corrupt and you have to repair it. Repair it use of compact and repair utility or you can try access repair software to repair your damaged database so that you can use it as before.