Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Application .mdb cannot find database .mdb

Status
Not open for further replies.
Jul 24, 2000
88
CA
In my Access XP development environment I have an application .mdb for the project code and a separate database .mdb for the database. When I initially created this, in the application .mdb I linked to the database in the database .mdb. Both .mdb's are in the same folder.

When I copied the the 2 .mdbs to the client's system - both into the same folder, the application switchboard appeared OK but as soon as I chose on of the switrchboard choices, I got an error - "There was an error executing the command". Not a very helpful message is it! Does anyone have any ideas about the cause of this? The project runs OK on my development system.

My thinking is that the application .mdb may not know where to look for the database .mdb. Is there a way I can make the connection?

Thanks for any help you can give.
RjB
 
Go to
Tools
Database Utilities
Linked Table Manager
to find or change the link to a db

Hope this helps
Hymn
 
Not sure it will hymn, but I'll give it a try and let you know.

Thanks for your help.
 
Did you ever get a resolution to this? I am experiencing a very similar issue and was wondering what the fix was.
 
Basically

In Access it is common to split a database from the application side called the front end and the data side called the back end.

The application front end side can be distributed to all local desktops, reside on the server. The data back end will always be located on the server and shared by all users.

The front end application accesses the back end by "linking" the tables.

If the data is moved to a different location, deleted, or security access is changed, the application front end will complain quite loudly that it can not find the data.

The problem is easily resolved by re-linking the tables. The link manager fascilatates this process. Point and click process. ...provided the data is still there.

This is when you go to your system or network admin guy or gal, or your database admin, and ask if anything changed. Database upgrade (with a new name), database move, new security.

If the database was deleted - "We run FrontEndApp.MDB, and no we dont run BackEndData.MDB" -- so let's save space. The three rules of IT - 1) backup, 2) backup, 3) backup.

Richard
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top