Database ultra slow

[Ed1]

Hi,

I'm sure if this question belongs to this topic....but here it goes.

My database is ultra slow after I changed it to a multi user database. I have a total of 20 fields in the database. 10 of those fields are the "original" fields and the other ten are a calculation version of the "original" fields. I do this to prevent people to be able to edit the data but can still be able to search. Would anyone know is the slowness from the calculation fields or from the multi user being selected.

Thanks in advance.

[Vaughan]

Make sure the calculation fields are "stored" otherwise they'll have to calculate each time they are searched.

If the calc fields use a function that contains either a global field or a related field they *cannot* be stored and you're stuck with the speed hit.

[Paolo]

You don't need the calculation fields for this purpose!

Just set up two layouts: one with fields with "Allow entry into field" selected, the other one, with "Allow entry into field" disabled.

Use the first in find mode to allow user perform find. When the find is performed send the user to the second layout in browse mode so they can't edit.

You can also control this setting up passwords (without having two layouts) or trought field validation.

---

For your speed issue I would check netwotk configuration, other applications running on the pc that host the database and so on...