Placing the database on the server is the best solution in a multiusers situation. Naturally, if the server go down, no users can access the data. There is not much you can do about it other to make sure that the server has a UPS.

If the server go down during a transaction, it could happen that a table or an index get corrupted or that partial informations get saved. There are some utilities in the Files section that could repair a damaged table or index. If partial informations are saved, you have the choice of restoring the database from a previous backup or building a utility that will scan the tables for referential integrity errors and ask a user what to do about them. Again, a good UPS on the server can avoid many problems.

HTH

>I like know your opinion, about the data enverioment that I using.
>On my systme the data directory is in a Work station diferente of the system directory, when the system begining the main program check out if in the machine there is a network driver called "R:\datos". It is due to I consider that which this way the administrator could have more control over the data.
>But some times due to the net the machine die no work, and it has to be shutting down and could happen that the information get wrong, this is one of the problem that I´ve had.
>What do you recomend me.???