By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,435 Members | 1,967 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,435 IT Pros & Developers. It's quick & easy.

3044 Error - weird CurrentDB failure

P: n/a
Scenaria -
Access 2000 FE - 2 clients
Access 2000 BE - on a network server.

Tiny little application, all tried and tested code. Worked fine until
this morning, when users began receiving the following error:

Error Number 3044

C:\Projects\MyClient\Data\MyClientData.mdb' is not a valid path. Make
sure that the path name is spelled correctly and that you are connected
to the server on which the file resides.

The code which caused the error is:

strSQL = "DELETE * from tblRotaReportData;"
CurrentDB.Execute strSQL

Later, it also fails on
DoCmd.OpenReport "rptFullRota", acViewPreview

The value of CurrentDB.Name in the Immediate pane is:

C:\Program Files\MyApp\Myapp.mdb

which is correct.

Anyone any ideas? I'm moderately desperate, but my clients are tearing
their hair out!

TIA

Edward

Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
te********@hotmail.com wrote:
Scenaria -
Access 2000 FE - 2 clients
Access 2000 BE - on a network server.

Tiny little application, all tried and tested code. Worked fine until
this morning, when users began receiving the following error:

Error Number 3044

C:\Projects\MyClient\Data\MyClientData.mdb' is not a valid path. Make
sure that the path name is spelled correctly and that you are connected
to the server on which the file resides.

The code which caused the error is:

strSQL = "DELETE * from tblRotaReportData;"
CurrentDB.Execute strSQL

Later, it also fails on
DoCmd.OpenReport "rptFullRota", acViewPreview

The value of CurrentDB.Name in the Immediate pane is:

C:\Program Files\MyApp\Myapp.mdb

which is correct.

Anyone any ideas? I'm moderately desperate, but my clients are tearing
their hair out!

TIA

Edward


This looks like the tables are not correctly linked to the backend.
Use the Linked Table Manager to check for the actual locations of the
links.

HTH
Matthias Kläy
--
www.kcc.ch
Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.