Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
WAN and Visual FoxPro Database (Data Accessing speed)
Message
From
16/10/1999 21:17:56
 
 
To
16/10/1999 18:43:11
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00276225
Message ID:
00277354
Views:
39
Well, Erik, I think you have a different problem than the one you state. . .

Does "almost SURELY" really sound definitive to you?

You remain unconvinced about the WHOLE issue, while I remain unconvinced that it has always been thusly.

Sorry, but I do NOT see a whit of carelessness in my statements on the issue.

regards,

Jim N

>Jim, I think this statement is a little careless.
>
>I have watched all of the discussions on the topic over the last year or so, and remain unconvinced. I can see huge performance advantages in 75% or so of my tables with the added tag on DELELETED(). But even on the ones that I don't see a difference, I add the tag anyway, because with their end-user reporting tools, my users might be querying the data in ways I had not anticipated.
>
>It is true, and I agree that in some instances, the extra tag will hurt performance, but the performance cost is tiny compared to the cost when you get it wrong the other way around.
>
>I don't want to start this same war over again, I just object to unqualified statements that sound decisive and definitive. To say that the DELETED tag is now a bad idea, and will slow down your apps is to general, and just plain not true.
>
>>Dan,
>>
>>That key on Deleted() is no longer a good idea at all. It will almost surely HURT performance of a VFP application!
>>
>>Some say that it has always been this way, suggesting that we were all misinformed when this "tip" originally made the rounds. I happen to disagree with that opinion, but have no way to prove it one way or the other. Just to be clear, I have NO DOUBT that an INDEX on Deleted() will most likely HURT an app.; I doubt that it has always been this way.
>>
>>Cheers,
>>
>>Jim N
>>
>>
>>
>>>Make sure the program is installed and running from the local machines.
>>>Make sure you're useing buffering. Make sure you're views are optimized sys(3054). Make sure you have a key on Deleted() on all your tables.
>>>
>>>You can also use coverage logging in the Debugger or just step through the program yourself to see which lines are so slow.
>>>
>>>HTH
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform