Winfried,

Tip: Don't use tablebuffering. This might consume too much memory. Instead use row buffing or no buffering at all. Using transactions might give the same result.

When using a NT server with opportunistic locking enabled, you might experience the same behaviour. Though the table might be opened shared, the NT server 'sees' that you're the only one who is using it, and allow the workstation to hold writebuffers until a second workstation comes in. To isolate the problem, you might want to try to set opportunistic locking of. See article Q150991 of the MS knowledge base.

Likely, the problem lies elsewhere in either the network environment or the specific circumstances of you application.

Walter,

>Hallo Chrstian,
>I had the same problem with a 16 MB File.
>Is I the VCX's a Listbox or Combobox in the game? What Index's set when transfer the file?
>I redisign my APP, use Grids instad List,Combos.
>
>Please say something
>
>Regards from Germany
>Winfried