Creating new fields in classes way Re: Telling tables what their fields are

[Ed Kleban]

Is there any reason I can't use methods such as CreateShortField or
CreateVarCharField to add additional fields after a table has been created
when using the Classes way?

I.e. instead of including the following line in the Table constructor...

  fSpanLen = new VULong( "FSpanLen" )

... simply create only some fields in the constructor and leave some field
variables such as fSpanLen equal to nil...  then much later, when needed,
come along and call...

    fSpanLen = myTable.CreateULongField( "FSpanLen" )

-----

If I do this, then presumably when fSpanLen is created it will have the same
number of records as all other fields of myTable, and the fSpanLen field
value for each row will be initialzed to 0 (SetBlank) when the column is
created, correct?




On 11/19/05 9:00 AM, "Ed Kleban" <Ed at kleban.com> wrote:
> 
> On 11/19/05 8:43 AM, "Ruslan Zasukhin" <sunshine at public.kherson.ua> wrote:
> 
>> On 11/19/05 3:22 PM, "Ed Kleban" <Ed at Kleban.com> wrote:
>> 
>>>> Tools as Valentina Studio and viSQL cannot use Class Way. NEVER.
>>>>     because they do not know structure of any db they going to open
>>> 
>>> Yes, but I want to "eat my cake and have it too" as we say here.  I want to
>>> use classes way to define my databases, and then be able to inspect them on
>>> disk with VS :)
>> 
>> You can this. No problems here.
> 
> Ah great!  Then I'm a happy camper.  :)
> 
>> I think you have missunderstnad.
>> 
>>     you can develop YOUR application with Class way.
>>     viSQL was developed with API way
>> 
> Yes, I did misunderstand.  Thanks for the clarification.  I see what you
> meant now after re-reading your comment in a different context.
> 
> Thanks!
> --Ed
>