If Indy is south of me Mike B. does that make it a 'Byte' to drive from
Detroit, Mi.?    

Sincerely,
Paul Dewey 










-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of MikeB
Sent: Monday, April 20, 2009 6:33 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Importing BIT Types

Since Indy is only a little 'BIT' north of Memphis...


----- Original Message ----- 
From: "Bill Downall" <[email protected]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Monday, April 20, 2009 5:11 PM
Subject: [RBASE-L] - Re: Importing BIT Types


> Speaking of which, Steve, are you finally coming to the R:BASE SAT in
> Indianapolis?
> Will your answer be a binary "yes" or "no,"  or are you going to 
> equivocate?
> It's a great place to get your own questions answered by a panel of 
> experts,
> as Jan described from the Portland session.
> Warning: if you don't show, we will shake our heads and say "Tsk, tsk, 
> tsk.
> Wills didn't make it again." If you do make it, you will have a great 
> time.
> Nominations are open for Friday night dinner venues, anywhere from the far
> west side of Indy (Plainfield) to downtown Indy.
>
> Sorry, though, you are not allowed to skip out Saturday for Pole Day at 
> the
> Motor Speedway. $5 entry fee at the track on Thursday, for practice, 
> before
> the official unveiling of R:BASE 9.0 Thursday evening. Stick around Sunday
> for the second day of qualifications.
>
> Bill
>
> On Mon, Apr 20, 2009 at 1:58 PM, MikeB <[email protected]> wrote:
>
>> The least storage space you can equivocate to would be TEXT (1) 
>> containing
>> T or F.  RBase has no BIT and VARBIT would be inapropriate.
>>
>>
>> ----- Original Message ----- From: "Wills, Steve" <[email protected]>
>> To: "RBASE-L Mailing List" <[email protected]>
>> Sent: Monday, April 20, 2009 4:50 PM
>> Subject: [RBASE-L] - Importing BIT Types
>>
>>
>> I am trying to import some records where there are source fields defined
>> as BIT, basically a logical ON||OFF.
>>
>> They are like this from the source db:
>>
>> ID   Description                      Bit1  Bit2  Bit3
>> ---- -------------------------------  ----- ----- -----
>> 1000,'My Record Description for 1000',False,False,False
>> 1001,'My Record Description for 1001',False,True,False
>>
>>
>> What might be the best way to handle their import into RB and should the
>> RB columns for the BIT fields also be BIT?
>>
>>
>> Thanks,
>> Steve in Memphis
>>
>>
>>
> 


Reply via email to