Distributing a database across a network

[PaulJK]

I have a database built in Office 2000.

The client wants it across a network but insists they do not want it split! They want it in a shared drive which everyone has access to via a shortcut.

The database is secured so I presume the Workgroup file will have to be on each PC and a shortcut to the one database on the server which is in a shared mode. Would the security I have implemented still work or would I have to de-secure so everyone has the same level of access.

They do not have Access on all PC's. IFor this to work I presume Access is needed both on the server and PC's

I understand if I purchase Microsoft Access Developers 2000 it has a feature where I can distribute a database to users without Access? However, am I right in assuming this needs the database to be split.

In the UK are there any suggestions on where I can buy Microsoft Access Developers 2000 ?

Many thanks.

 

[hamiltonk]

Re:

Why not just house the data on the server, and link it to the tables on the server. This way you can setup several security settings or just one depending on what the shell application needs.
The only downside would be maintenance, depending on the number of users.

 

[PaulJK]

Forgive me. I am not sure how this could work. Would it require the database to be split?

 

[Pat Hartman]

Nothing requires that the database be split. Splitting the database is recommended because it increases the stability of the application and reduces network traffic. I can almost guarentee corruption problems in a shared db. All it takes is for one person to leave the db open while rebooting or have a network blip. Make sure to backup at least twice a day.

As to the developer's edition for A2K - I don't think that it is available any longer. You will need to find it on ebay or from some source other than Microsoft who has old stock.

All the developer's edition does is to give you a license to distribute the runtime version of MSAccess.exe. It doesn't modify your application at all. You must be aware of its constraints though. You MUST have complete error trapping and that means NO macros. Any error will cause the db to simply shut down. You must also provide custom menus since many of the standard menu options are not available while running under the runtime engine. To get a preview of how your application will act, open it with the /runtime switch. Search here for many posts and warnings on the Access runtime environment.

I don't know what problem your customer has with splitting the db but he is asking for trouble by insisting that it remain a monolith.

If you split the db, you can actually use a newer version of Access as the runtime engine (which will be easier to obtain). The be can be left as A2K and you can keep two versions of the fe. One in A2K which is the master and the only one you should change and the other in A2002 or A2003 format which is distributed and run on the PCs with the runtime engine. I haven't experimented with this but it may be possible for the A2002/A2003 runtime to run an A2K version.

 

[Pat Hartman]

Also, it doesn't matter what OS the file server is running, nor does the file server require Access to be installed. The application does not run on the server. It runs on the client PC. The entire db is sent over the wire to the local PC and run there.