V4RB Windows VarChar Error 351

[Ruslan Zasukhin]

on 2/1/04 4:27 PM, Erich Geiersberger at erichg at mcmm.com wrote:

> We have made Client-Server test during the last weeks with V4MD and
> we also had problems with this message. While I am not sure if it
> works in the same way with V4RB, here are some ideas:
> 
> Error 351 occured quite often, when a client using read locks wrote
> to a record and tried to read from the same table immediately
> afterwards.
> 
> This might also be related to the fact that our database gets flushed
> after each write.
> 
> The server debug window showed an error 351 "VarChar Field corrupted"
> immediately followed by a "error 0, no error". After a first
> occurance of that error, it happened more often, but went away after
> a server restart.
> 
> I have checked my database a couple of times and found NO errors in
> it when that happened.
> 
> After setting most of our cursors to no read locks, it occured a lot
> less often.
> 
> I am not absoultely sure what condition makes it happen, but I am
> quite sure that the message is wrong. It seemed to happen when we
> tried to read from a freshly edited record while it got flushed to
> disk.

Agree Erich, that message wrong.

Igor, try to reproduce this.
Erich have give good details it seems.

And 

1) Cindy use not Valentina server but own one
2) as I see, he get db files really corrupted.

So his problem should be other

-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------