[VSERVER/V4RB] - Vserver on X.4.6, V4RB 2.3 Client Connection

[Russ Tyndall]

Using V4RB 2.3b10 on a Win XP client and Vserver 2.3 (on Mac OS X.4.6):

When connecting to a Vserver 2.3 served db on X.4.6 from an XP V4RB 2.3b10
client, does the V4RB app need to do anything special to account for
Endianess or encoding, etc.?

This is what I am experiencing, although I do not know the cause.

I have an in-house app that's been used fairly heavily by two Mac OS X
machines, and is working pretty good.

Yesterday, I began to tweak the Win32 version of the client app.

Unfortunately, whenever I open the db from Win32, the db becomes unusable by
the OS X clients.  When the OS X apps try to insert a record, all the
string/varchar fields are not properly updated; numeric fields are updated
properly.  ThrowExceptions is set to True, but no exception occurs.  It's
just the fields are updated with "bad" data.

A diagnose from Vstudio reports this problem:

*****

==========> Field: item_notes , type Text
    .RecID: 1440. Segment: 1441. already in use.

******

Interestingly, all the Win32 app does is open the DB from within a Vserver
object, and update a "last login" type field that resides in a different
table.

If I replace the db with a backed up copy, I can then everything works great
until I connect from Win32; then the problem starts again.

Any suggestions?

-- 
Russ Tyndall
Wake Forest, NC