Jay:

Ok I take your point.

BTW, if tabs are used as field delimiters and c/r's are used as record
delimiters and all field data excludes tabs, c/r's, commas and " --inch
marks then this format would be instantly readable in xcel or appleworks
spread sheets as a pure tab-delineated text file...

During development, spreadsheets are very useful to quickly verify if all
the fields/records are being written/stored in the right places... There is
a limit of 64K lines/records in xcel....


on 7/24/04 2:37 PM, Jay Reeve at jayreeve@... wrote:

> Michael,
> 
> Good point, but these are all easily controllable for edit field entry,
> so tedd's assertion is correct in practice.
> 
> e-e
> =J= a  y
>  "
> 
> On Saturday, July 24, 2004, at 01:32  PM, michael evans wrote:
> 
>> on 7/24/04 2:06 PM, Jay Reeve at jayreeve@... wrote:
>> 
>>>> If I use HEX single byte delimiters, then I could have available to
>>>> me
>>>> for use values 01 to 1F -- 31 different flags for controlling data.
>>>> Remember, the lowest value obtainable by the user in edit field entry
>>>> is a space (SP) with a HEX value of 20 -- thus everything below that
>>>> is up for grabs.
>> 
>> This is not entirely true?
>> 
>> What about <tab>=chr$(9), <l/f>=chr$(10), and <c/r>=chr$(13)?
>> 
>> Cheers,
>> 
>> -----------------------------------------------------------------------
>> -----
>> Michael Evans
>> -----------------------------------------------------------------------
>> -----
>> 
>> --
>> 
>> 
>> 
> 
> 
> --
> To unsubscribe, send ANY message to: futurebasic-unsubscribe@...
> 

Cheers,

----------------------------------------------------------------------------
Michael Evans
----------------------------------------------------------------------------