Linking to back end on a web server ?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Does anyone know how to link my front end to a back end sitting on a web
server?
There is a userid and password required for the web server and the back end
is also protected by an Access password.
Can this even be done?

Thanks.
 
mscertified said:
Does anyone know how to link my front end to a back end sitting on a
web server?
There is a userid and password required for the web server and the
back end is also protected by an Access password.
Can this even be done?

Thanks.
Click to expand...

No. An Access link requires being able to see and open the back end file
like you would on a local drive or local network. An internet connection
over HTTP does not allow for that.
 
I do see this server in 'My network places', so i believe it's on the network.
Are you saying to get to the data, I'd have to open an ADO connection and
read the data via ODBC?
 
If you can see the server, you should be able to create a DSN and link to
it. Once you've linked to it using a DSN, you should then be able to change
that DSN-based connection to a DSN-less connection.
 
mscertified said:
I do see this server in 'My network places', so i believe it's on the
network. Are you saying to get to the data, I'd have to open an ADO
connection and read the data via ODBC?
Click to expand...

Well, if you are talking about a web server that is on your local network
then as far as Access is concerned it is just another server. The fact that
it is a web server is irrelevent. You just need appropriate permissions to
the folder where the Access MDB back end is located.

I thought you wanted to connect to the MDB on a web server "over the
internet". That is not possible.
 
Do you know how to create a DSN?
I went into Control-panel settings and tried but it expects me to browse to
the database and I cannot get into the server to display the folders
Also, assuming I can create the DSN, how do I use that to link to the back
end tables?
 
There must be something 'different' about this server than others I can
access because in 'network places' I cannot display any folders within the
server.
 
mscertified said:
There must be something 'different' about this server than others I
can access because in 'network places' I cannot display any folders
within the server.
Click to expand...

That would be completely normal if that server has no shared folders that you
have permissions to.
 
Rick Brandt said:
That would be completely normal if that server has no shared folders that
you have permissions to.
Click to expand...

Or if all of the shares are hidden (by putting $ at the end of their name)
 
You'll have to talk to the administrator of that server. Either no share has
been created, the shares are hidden, or you haven't been given permission to
even see the shares. Even if you can't browse to the file (such as will be
the case if the share is hidden), you can type the full path to the file.

Once you've create the DSN, you go through File | Get External Data | Link
Tables and select "ODBC Databases()" from the Files of Type list.
 
Thanks for your advice so far. The saga contuinues... I set up a System DSN
in ODBC connections.
When I do the File--Get External Data and select the DSN, here is what I
get, any ideas? I don't know what it means by "<SQL Database>".

"You cannot use ODBC to import from, export to, or link an external
Microsoft Jet or ISAM database table to your database. (Error 3423)"

You are attempting to link, import data from, or export data to either an
external Microsoft Jet table or an external ISAM database table (for example,
dBASE, Microsoft® FoxPro®, Paradox, or Btrieve), but you have selected <SQL
Database> as the data source. You must select the appropriate data source for
the data you are attempting to link.
 
I was able to set up the link if I just linked the table as an mdb file not
as an Odbc file. I guess that means it's not using the DSN at all. Is there
any advantage/disadvantage either way?
 
mscertified said:
I was able to set up the link if I just linked the table as an mdb
file not as an Odbc file. I guess that means it's not using the DSN
at all. Is there any advantage/disadvantage either way?
Click to expand...

You cannot link from Access to Access using ODBC. So the advantage of not
using ODBC is that it works whereas using ODBC would not work :-)
 
Back
Top