> > >> I have to do this calculation, because the raw data is just times when > the > >> emp. enter work and leave work. > > > I thank you all for your replays, I thing my situation is a bit more > complicated at that. > First my raw data is not mine. > The table look like this > Emp. date1 hour1 date2 hour2 dep job > N6 D8 N6 D8 N6 N6 N6 > ......... > So my calculated end result is tables and views in forms to this tables. > > My problem is multi user related. > > Is there a good way to solve this??? > > Best regards > Per Simmersholm Wow, you do seem to have a problem, and it seems to be a matter of design, and not so much a matter of programming. Since raw data are not yours, you can scan them every once in a while (hourly, perhaps) and see what's new. Keep a marker on what you processed and what not. In "processing" I mean creating/updating a paralel table with data made as ready as possible for further calculations - use the table shown above and the schedule to calculate normal hours, overtime, shift, kilos, quality mark, anything, totalled on worker+day so you don't have to calculate it over and over. Have this intermediate table indexed on worker, day, department and/or whatever you find useful. Use this table to create views/cursors from. This saves you overhead of processing raw data every time; you process it once and have your data ready. After that, anyone can access this half-prepared data and have a SQL selection (or a view, which amounts to about the same) and I assume it'd be quick enough. If you insist these calculations be written into tables, put the calculated tables to user's local disk, so you have no network colision problems.