Large field not getting recorded
Boaz Bezborodko
boaz at mirrotek.com
Wed Mar 24 11:27:51 PDT 2010
Kenneth Brody wrote:
> On 3/24/2010 1:04 PM, Boaz Bezborodko wrote:
>> A few days ago I wrote about having problems loading a file into MEMO.
>> Instead of using MEMO I was told about WORDWRAP. But I am now getting a
>> different problem.
>>
>> I changed the memo field from a 16,memo to a 148,*. But when the record
>> is being recorded 201 is getting cleared. When I go through the table
>> using DEBUG the program is properly loading 201, but when I look at it
>> again afterwards, 201 is blank.
>>
>> I thought that maybe this was a problem or bug due to switching the
>> field from memo to *. SO I tried creating a new field also with 148,*
>> and loading both with the same data. In both cases the fields are
>> loaded with the data during an import, but are empty when I look at them
>> later.
>>
>> At no point do I do anything with these fields other than when I load
>> them with the data.
>>
>> What could be causing this? It's really holding me up on my programming
>> since my code is working all except for this.
>
> Try a simple test ---
>
> Make an input processing that does one thing -- assigns a value to
> those "long" fields. Run dclerk with that input, and without any
> automatic processing. Does it still fail? If so, contact fpsupport.
> If that works, then there's probably something in your processing
> that's blanking out those fields.
>
Another DOH!!! (That's two big ones for today.)
I was entering the data into the field I was standing on instead of into
a lookup free record that it's supposed to go.
Jeez...I think I must be lacking sleep or maybe it's that my wife gave
me a cup of coffee this morning, something I don't normally drink.
To paraphrase Lloyd Bridges:
"It looks like I picked a bad day to START drinking coffee."
More information about the Filepro-list
mailing list