Problems sharing...

  • Thread starter Thread starter Ted
  • Start date Start date
T

Ted

I have a database that I need to share between 3 other computers. These
computers do not have Access installed, so I created installations with the
runtime version of Access for these computers. I want to install the entire
database (front and back end) on one computer, then install just the front
end on the other 2 computers and have them all show the same data. However,
this isn't working...I am unable to point the other 2 computers to the back
end through the network, presumably because this can't be done with the
runtime version of Access. If someone knows what I'm doing wrong here, fill
me in please! Thanks in advance
 
Ted said:
I have a database that I need to share between 3 other computers. These
computers do not have Access installed, so I created installations with the
runtime version of Access for these computers. I want to install the entire
database (front and back end) on one computer, then install just the front
end on the other 2 computers and have them all show the same data. However,
this isn't working...I am unable to point the other 2 computers to the back
end through the network, presumably because this can't be done with the
runtime version of Access. If someone knows what I'm doing wrong here, fill
me in please! Thanks in advance
Click to expand...

If you create the links by going through Network Neighborhood - Entire
Network then they will work on all three computers without having to change
them. The connect string will look like...

\\ComputerName\ShareName\YourFile.MDB

....instead of...

C:\FolderName\YourFile.MDB
 
I tried this and got a run-time error. This was without a runtime version
installed. With a runtime version installed, the database will run but only
if the back end is on the local computer in the same directory as the front
end. It will not work any other way. I'm at a loss here...there has to be
a way to do this but I'm having a serious brain cramp..
 
Ted said:
I tried this and got a run-time error. This was without a runtime version
installed. With a runtime version installed, the database will run but only
if the back end is on the local computer in the same directory as the front
end. It will not work any other way. I'm at a loss here...there has to be
a way to do this but I'm having a serious brain cramp..
Click to expand...

Sorry, but this isn't much to go on. *When* did you get an error? When
you attempted to change the links? When you attempted to use the linked
tables after changing them? What was your procedure to change the links to
a UNC path instead of a drive path?
 
I'll try to clarify what I'm saying here....I am not able to link the table
(back end) of this database (which is installed on computer 1) with the
front ends which are installed on computer 2 and computer 3, all 3 of which
use the runtime version of Access. No matter what I do, I'm not able to do
this.

I created the link to the front end through network neighborhood, clicked on
the shortcut, and attempted to enter data into the database..that's when I
got the runtime error. This database is split, and I am attempting to
install the front end only on 2 of the 3 computers. I want to link that
front end to the back end on computer 1 where it is installed in a shared
folder. I can't find any way to (1) install my front and back end on
computer 1, (2) install only the front end on computers 2 and 3, (3) link
the front ends of computers 2 and 3 to the back end which is installed on
computer 1. I need all 3 computers to show the same data. See what I mean?
I'm afraid that because I'm using the runtime version of Access that I'm
beating my brains out here in vain. Am I?
 
Somebody???

Ted said:
I'll try to clarify what I'm saying here....I am not able to link the table
(back end) of this database (which is installed on computer 1) with the
front ends which are installed on computer 2 and computer 3, all 3 of which
use the runtime version of Access. No matter what I do, I'm not able to do
this.

I created the link to the front end through network neighborhood, clicked on
the shortcut, and attempted to enter data into the database..that's when I
got the runtime error. This database is split, and I am attempting to
install the front end only on 2 of the 3 computers. I want to link that
front end to the back end on computer 1 where it is installed in a shared
folder. I can't find any way to (1) install my front and back end on
computer 1, (2) install only the front end on computers 2 and 3, (3) link
the front ends of computers 2 and 3 to the back end which is installed on
computer 1. I need all 3 computers to show the same data. See what I mean?
I'm afraid that because I'm using the runtime version of Access that I'm
beating my brains out here in vain. Am I?
Click to expand...
 
Ted,

I think that what Rick wrote about using the UNC paths for
the linking is probably the key to your problem. You say
that you used Network Neighborhood to link the front end.
Was that in the Linked Table Manager???

On your development machine that is storing the backend, go
to the Linked Table Manager and look at the paths for the
linked tables. If they start with "C:\" instead of
\\SomethingOrOther, this is your problem. If this is the
case, check the "always prompt for new location" and then
Select All to reset the paths. In the next window browse to
the shared folder through Network Neighborhood here and it
should set up the correct UNC path which will always start
with \\ and then a computer name. When you are done, reopen
the Linked Table Manager and verify that the new path starts
with \\.

Gary Miller
Sisters, OR
 
I completely understand what both of you are saying, and appreciate your
help. However, I am developing this database off-site and that's the
problem. I can make it work on my network but it's not the same as the
network it will be installed on, and I have no way of linking the tables
from within the freaking runtime version of Access that I know of...unless
there is some trick that I am unaware of. This is what is killing me. I
need a way of doing this on site after I install the database...and I feed
nothing but a sinking dreadful feeling that I'm never going to get it
accomplished! Maybe I'm wrong, and hopefully someone out there will prove
me wrong. Thanks in advance for any and all help!
 
Ted said:
I completely understand what both of you are saying, and appreciate your
help. However, I am developing this database off-site and that's the
problem. I can make it work on my network but it's not the same as the
network it will be installed on, and I have no way of linking the tables
from within the freaking runtime version of Access that I know of...unless
there is some trick that I am unaware of. This is what is killing me. I
need a way of doing this on site after I install the database...and I feed
nothing but a sinking dreadful feeling that I'm never going to get it
accomplished!
Click to expand...

Relink Access tables from code
http://www.mvps.org/access/tables/tbl0009.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Ted said:
I completely understand what both of you are saying, and appreciate your
help. However, I am developing this database off-site and that's the
problem. I can make it work on my network but it's not the same as the
network it will be installed on,
Click to expand...

Ok, that is new information. None of your prior messages indicated that
you were attempting to set this up while on one network and then distribute
the files on a different one. Tony's solution will take care of it.
 
Back
Top