That may well be true about BROWSE. My point remains the same, though: is that the user's fault or the vendor's? To me the answer is clear, and that isn't Microsoft-bashing. I would say the same of, I don't know, Intuit, if a special character typed into an amount field corrupted your financial data file.
>There's only so much that VFP can do internally to stop corruption. IMO, the single most dangerous command for causing corruption is BROWSE.
>
>>Should it be possible to design an application so poorly that files in the product's own format get corrupted? That's giving the vendor quite a pass IMO.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only