Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Chr(13) in Memo fields being redefined in query?
Message
 
 
To
08/03/2012 11:05:51
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Visual FoxPro:
VFP 8 SP1
OS:
Windows 7
Miscellaneous
Thread ID:
01537537
Message ID:
01537628
Views:
36
>It's not a case of insert into....Select out of. You asked about how the records were saved, so I told you. These records are held in two tables until they are needed.
>
>So, having said that - when I look at the 'master' table, the Chr(13) is there. When I look in the intermediary table (dupwk) the Chr(13) is there. When I looking the cursor (testbook) it is not.
>

That's weird. If the chr(13) is there in the table and not in the cursor, then I don't know what may cause it. Just in case, try playing with SET MEMOWITH setting.

>
>>>The saving of individual records are done with an Insert
>>>
>>>The SQL that pulls the cursor is :
>>>
>>>Select Val(b.seq) As qstnum, b.cat, a.script, a.stem, a.respa, a.respb, a.respc, a.respd,;
>>> b.itmnum, a.scriptim ;
>>>From convatc a, dupwk b;
>>> WHERE a.itmnum = b.itmnum;
>>> INTO Cursor testbook;
>>> ORDER By qstnum
>>>
>>>Script and Stem are both memo fields
>>>
>>So, right before INSERT command the memo has chr(13) and right after select it does not?
If it's not broken, fix it until it is.


My Blog
Previous
Reply
Map
View

Click here to load this message in the networking platform