[V4Rb Client] problem

[Ruslan Zasukhin]

on 9/12/03 18:22, Charles Yeomans at yeomans at desuetude.com wrote:

>> Charles,
>> 
>> But WHY you want to use this in CLIENT ?
>> 
>> BaseObject API should not be used in CLIENT.
> 
> VBaseObject expresses the structure of a table, and that's what I want.
> Instead of hard-coding strings in my code, I can, for instance, use
> Table1.SomeField.Name to get the name of a field.

Yes, and BaseObject API works in CLIENT from point of view of structure.


> I have a set of classes for building SQL queries.  A DBQuery class has
> methods like AddTable(theField as Field).  I have a bunch of small
> classes for building WHERE conditions.  For example, a WHERENodeEquals
> class has many constructors, overloaded by VField subtype -- for
> example, WHERENodeEquals(theField as VULong, value as Integer).  By
> using the VField objects obtained from VBaseObject, I can get the
> compiler to do the majority of my error-checking.  So, for me, what's
> useful is the ability to get VField objects that contain the field name
> and type (as expressed by subclasses).

Okay, I see you have strong reasons :-)

> I agree that one should not use VBaseObject to work with database data;
> indeed, I suggested that the ability to do this be removed from
> VBaseObject a long time ago.  But if we can't use VBaseObject to work
> with database structure, then maybe V4Rb should just implement the RBDB
> interface instead.

No, this is not our way :-)

Okay, so we need to improve CLIENT to RecID field also.

-- 
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
-------------------------------------------------------------