Sharing an Access Database on the Internet

[djs45uk]

I have an Access database with lots of tables, queries, forms and reports used by all teachers at our school.

I have put the database onto our Internet server so that it can be accessed from anywhere. When you click the link to the database and choose 'Open' from the dialog box, it downloads a copy of the DB into the local temporary internet files.

Any changes that user makes to the database are only saved to the local machine and not to the shared database on the server.

How can I make the database accessible to all and ensure that their edits are visible to all?

Many thanks
Daniel

 

[Guitarreg]

To make sure you are updating the correct data; I would first separate the forms from the actual data. Then have your users download the mdb/mda, MyForms.mdb that holds the forms that are linked directly to your odbc data source MyData.mdb which is stored on your server.

 

[BNPMike]

When you click the link to the database and choose 'Open' from the dialog box

I don't about others but I cannot immediately understand what you are doing here. You are using the Internet - how exactly? It looks as though you are getting some type of ftp connection. If so, you need to tighten up the security on your server.

 

[Amiel]

Incredible.

Why not just use the Access database in a more conventional and less complex way by making it available over your nework rather than through an HTTP browser interface as you describe. Don't use the local web.

If you wish to make the database available using a browser interface you will need web pages that display the data; this is in addition to the very capable database that you have already created.

You can get help creating the client/server program that you are probably not very far away from at this point. Judging by your description of the problem you should probably first simplify this problem by eliminating the web interface entirely - for this version anyway.

With Access forms on each client machine (the database splitter does that) and a shared Access database at your 'server'. You can have your first version of this program functional in no time. With the web enabled version to follow.

Take a look at the database splitter. The 'wizard' seperates the database into two parts isolating the data from the forms that are used to view and modify the data.

Use this tool and play with the results for a day or so.
final steps include setting permissions for the directories on the server machine to allow access to specific users and deny access to others. A whole 'nuther world which you will have to explore - as the architect of this masterpiece.

This is the traditional approach to development. This program won't be ready until you have tested it as fully as you know how; duplicating conditions of actual use.

Once the client /server version is complete you'll want to begin to consider tackling web-enabling the application.
And even then tackle just the reports for starters.

Hope this helps.

Amiel
amielzz@netscape.net

 

[Guitarreg]

Did you get a chance to look into using linked tables yet? If you have your data stored on the network e.g. \\MyDataLocation\MyData.mdb which will hold all your tables, and the Forms databse with all your queries and macros that your users click on e.g. c:\temp\MyForms.mdb. Once you link the MyForms.mdb using the File menu => Get external data => Link tables => \\MyDataLocation\MyData.mdb, then Select all your tables. They will always be linked and the data will be stored on your server. If you need to change the location of the data, you can use the tools menu, database utils, linked table manager...
Reg