Remote copy of database

[Guest]

I am in the process of learning to use Access. An associate made a copy of na
old er not used database that I could play with and learn a bit on.He
downloaded it to his laptop and then remotely transfered it to my
computer.Everything opens fine on his laptop but on my computer when I go to
open one of the Access databases ot says it can't find the linked backend
..mdb files? Is there somethjing I'm not doing correctly? Is there a simple
solution to this?

 

[Joseph Meehan]

I am in the process of learning to use Access. An associate made a
copy of na old er not used database that I could play with and learn
a bit on.He downloaded it to his laptop and then remotely transfered
it to my computer.Everything opens fine on his laptop but on my
computer when I go to open one of the Access databases ot says it
can't find the linked backend .mdb files? Is there somethjing I'm not
doing correctly? Is there a simple solution to this?

That sounds like it is a "frontend" database. When Access is shared,
it is best to make one database with all the data in it and leave that copy
on a server. It is called the backend. The other half of this split
database are databases located on the user's machines and these contain the
forms, queries and reports. They link to the back end to get the data.
This arrangement makes sharing information faster and more reliable.

My guess is that backend is either located on your associates laptop and
you did not get the copy of it, or his laptop is on a LAN you are not on or
you don't have the same "path" to that location where the backend is stored.

 

[Douglas J. Steele]

The recommended approach for Access applications is to split the application
into a front end (containing the queries, forms, reports, macros and
modules), linked to a back end (containing the tables and relationships). It
sounds to me as though your associated only gave you the front end
application, and didn't include the back end (or else the back end has
moved, or been deleted).

Look on the Tables tab. Are there little black arrows pointing to each of
the icons? If so, then you definitely need to look for an associated back
end database. Go to the Immediate window (Ctrl-G), type:

?CurrentDb.TableDefs("NameOfTable").Connect

and hit Enter (replace NameOfTable with the name of a table that has the
arrow beside it). That should tell you what database it's expecting as its
back end.

 

[Guest]

Thanks

The recommended approach for Access applications is to split the application
into a front end (containing the queries, forms, reports, macros and
modules), linked to a back end (containing the tables and relationships). It
sounds to me as though your associated only gave you the front end
application, and didn't include the back end (or else the back end has
moved, or been deleted).

Look on the Tables tab. Are there little black arrows pointing to each of
the icons? If so, then you definitely need to look for an associated back
end database. Go to the Immediate window (Ctrl-G), type:

?CurrentDb.TableDefs("NameOfTable").Connect

and hit Enter (replace NameOfTable with the name of a table that has the
arrow beside it). That should tell you what database it's expecting as its
back end.

 

[Guest]

Douglas, I can't even get that far I click to open the database and almost
immediately get this error message about not linking to backend
database.mdb.Once I'm in this error message it then takes me to some type of
coding window.Once I click that to close it says that will stop the debugging
and then thats it. Is there any hope for me?

 

[Douglas J. Steele]

Once debugging has stopped, try what I suggested.

Another possibility is to hold down the shift key while you're opening the
database: that prevents any start-up processing from happening.