Remote Database problem

[Chris]

Ok My problem is that I have a buisness and so we have a database of our
clients details and our server details, IP's what on them etc. Now
currently (were a new buiness) me and my co-owner have this database and
i will update it and then send it to him as its updated. Very bad.

Now i accedently made a second file of mine called h4u_data.ADP instead
of .MDB. So i open this up and it has a connection thing to conenct to
ip with admin login etc etc. Now im quessing i could have my database
remotly, and anytime we want to view it, just laod this .adp file,
connect, view, change add etc then close connection and when my co-owner
goes on it say the next day, the new client is there and the old client
is gone, hence updated.

Now my problem is i have no idear how to do, as in set up some kind of
server for this Database. Now our servers are on Win2003 Enterprise and
IIS is running with .aSP php etc na di know i can access IIS as we set
up a site and tested.

Thanks

P.S i googled it and all i found was getting data for use on a .asp
page, this is nothing to do with .aspo or anything, jsut wanted a remote
database to conenct to though access thanks

 

[Chris]

BTW were using Office XP at home but office is not installed on the
server but we could we have full root acces as its our own server.
Thanks again

 

[Brennan]

Hi Chris:
It sounds as if you have created an Access Data Project
which is basically an Access Front end and SQL Server
Backend. That is probably why you are being prompted for
connection information. The application is looking for a
SQL server database

Is this what you intended to do? If so you'll have to set
up SQL server

Brennan

 

[Chris]

ok basically, i made this .adp file accedently while playing around and
i wonderd if i could put this database on a server, and then open up
access and connect to this database and then look at the data, so its
just the same as getting all the data thats in my database on my
harddrive but its getting it from the database on the server, do you
understand? im not sure if its possible, but i would of thought it would be

 

[Rick Brandt]

ok basically, i made this .adp file accedently while playing around and
i wonderd if i could put this database on a server, and then open up
access and connect to this database and then look at the data, so its
just the same as getting all the data thats in my database on my
harddrive but its getting it from the database on the server, do you
understand? im not sure if its possible, but i would of thought it would be

It's not. An Access (Jet) data file is just a file. Anything that your app
does with it is done locally because your local PC is the only one running a
program. The server is just "serving" the file. Access (on your PC) asks for a
piece of the file and the server provides it. It's nothing more than a remote
hard drive.

With a server-based back end (like SQL Server) there is a program running on the
server and your client application sends requests to that program and that
program responds to those requests. In doing so it might need to do a lot of
processing work (on the server) before sending back the results.

The idea of an ADP is an Access application more tightly integrated to SQL
Server than an MDB. You can place your Jet file on a server and then create
another Access file that links to it and uses the data remotely over the
network. This is how the vast majority of Access applications are set up. You
just can't do that with an ADP. You need to use an MDB instead.

 

[Chris]

ok, got any good sites for a tut on that??

It's not. An Access (Jet) data file is just a file. Anything that your app
does with it is done locally because your local PC is the only one running a
program. The server is just "serving" the file. Access (on your PC) asks for a
piece of the file and the server provides it. It's nothing more than a remote
hard drive.

With a server-based back end (like SQL Server) there is a program running on the
server and your client application sends requests to that program and that
program responds to those requests. In doing so it might need to do a lot of
processing work (on the server) before sending back the results.

The idea of an ADP is an Access application more tightly integrated to SQL
Server than an MDB. You can place your Jet file on a server and then create
another Access file that links to it and uses the data remotely over the
network. This is how the vast majority of Access applications are set up. You
just can't do that with an ADP. You need to use an MDB instead.

 

[Rick Brandt]

ok, got any good sites for a tut on that??

Make one file with nothing in it but your tables and place it on the server.
Make another file with everything except for tables and put that on your local
PC. Then go to...

File - Get External Data - Link Tables

....in the main menu and in the resulting wizard navigate to your file on the
server and choose "Select All" in the tables tab. Your done.

There are some different ways you should go about doing things to "optimize"
your app for running in this fashion, but that it the basics of setting it up.