On Fri Apr 25 2014 Eric Abrahamsen wrote:
> It wouldn't be hard to store information about a *single* message: you
> could concatenate message id, subject, group name, and whatever else
> into a single string, if necessary. But to be really useful, I was
> hoping to get a value like:
>
> '(((23423
Gijs Hillenius writes:
> On 24 Apr 2014, Eric Abrahamsen wrote:
>
>> "Roland Winkler" writes:
>>
>>> On Thu Apr 24 2014 Eric Abrahamsen wrote:
I'm trying to create a custom xfield for records that is a list, not
a string. So far as I can tell, it's only possible for xfield values
On 24 Apr 2014, Eric Abrahamsen wrote:
> "Roland Winkler" writes:
>
>> On Thu Apr 24 2014 Eric Abrahamsen wrote:
>>> I'm trying to create a custom xfield for records that is a list, not
>>> a string. So far as I can tell, it's only possible for xfield values
>>> to be strings. Is that correct? Is
"Roland Winkler" writes:
> On Thu Apr 24 2014 Eric Abrahamsen wrote:
>> I'm trying to create a custom xfield for records that is a list, not a
>> string. So far as I can tell, it's only possible for xfield values to be
>> strings. Is that correct? Is it possible to circumvent this at the
>> momen
On Thu Apr 24 2014 Eric Abrahamsen wrote:
> I'm trying to create a custom xfield for records that is a list, not a
> string. So far as I can tell, it's only possible for xfield values to be
> strings. Is that correct? Is it possible to circumvent this at the
> moment?
By default, the values ox xfi
I'm trying to create a custom xfield for records that is a list, not a
string. So far as I can tell, it's only possible for xfield values to be
strings. Is that correct? Is it possible to circumvent this at the
moment?
Thanks,
Eric
