Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Macro expansion
Message
From
13/09/2001 11:01:10
 
 
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Miscellaneous
Thread ID:
00554002
Message ID:
00555939
Views:
30
>No need to apologize, Alan. I'm glad you discovered what was causing it. My thoughts and prayers are with your company for all your New York employees and their families.
>
DITTO exactly



>>My humble apologies to everyone for not getting back to this sooner. With one thing and another, I haven't been spending much time on this. The company I work for is called "AON", and we had 1100 people at the top of tower two in out New York office. I guess I've been listening to the news more than programming lately.
>>
>>Anyway, I took a look at this and it appears that when I was fixing another bug before recompiling in version 7, I must have inadvertently changed something in the memo field that affected the results of this thing. You are both right. As stated, it won't have run under either version. I still don't really remember doing it, but it seems I added a space between the commas and the semicolons in the memo field (I'm the only one here doing this stuff, so it had to be me). The code that loaded it into the variable was a series of strtrans()'s stripping out linefeeds/returns and semicolons (this being the case, why they were typed in is beyond me). The addition of the space meant that the ",;" was not found, and the semicolons were not stripped out.
>>
>>Mea Culpa, and again, I apologize to one and all.
>>
>>Alan
>>
>>>>SNIP
>>>>>I get the syntax error in both VFP6 and VFP7. What results do you get?
>>>>
>>>>Rick,
>>>>
>>>>I tried similarly and got error on both too.
>>>>
>>>>My guess was that it *could* have been compiled on-the-fly in VFP6 but suppose that would be evident in theprogram.
>>>
>>>I dunno, Jim. At the moment it's a mystery to me why it works in his app under VFP6. That's why I asked him to post the code that assigns the value of the memo field to his memvar. You'd expect a simple x = myTable.cMemoField command, but maybe it's being run through a parser that strips off the semi-colon / carriage-return / line-feed characters, in which case it could be that something in the parser is working under VFP6 but not under VFP7. It'll be interesting to see what results he gets if he runs the little test program I posted.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform