Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Speeding up code-scan,update (follow-up from last Thursd
Message
From
19/08/2008 14:30:23
 
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Environment versions
Visual FoxPro:
VFP 8 SP1
OS:
Windows 2000 SP4
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01340003
Message ID:
01340045
Views:
10
>>>>I thought sCur is a pseudonym for the c7. Otherwise good catch! I'm wondering why Beth didn't notice?
>>>
>>>Even though,
>>>Why Beth not get the values she wants directly in SELECT than update some fields lately?
>>
>>Good point again. Since the only reason for C7 existance seems to be to be used in UPDATE, when why do we need extra fields at all? We just need one field and that's all.
>
>I' taking the Lotus pose start meditate with very loud "OHMMMMMMM" and hope I'll new what the Beth wants :-)))))))))))

lol,

sCur is the pseudonym for the c7.

Yes, I have the enginbehavior set to 70, because I have not had time to go through ALL the reports that were done and fix the "blinking" code so that it does not fail in 8.

I will also look at putting in joins, instead of wheres. But I need the records to only be the ones where the dateappr is NOT empty, I can not have any records that are not approved.

Thanks for all the suggestions.
Beth
Previous
Reply
Map
View

Click here to load this message in the networking platform