On Wed, Jun 5, 2019 at 7:59 PM Bill Anderson <[email protected]> wrote:
> DECLARE Next(1, 1) > Next(1) = .F. && Boom! > > Bill Anderson > Thank you for contacting ProFox technical support. Your email is important to us. Please read this entire message before replying, as our options have recently changed. Due to unprecedented email volume, replying to your message may take longer than usual. Thank you for your patience. Please keep checking your emails, as email is replied-to in the order in which it is received, more or less. In order to better assist you, we ask that you consider supplying the following information: Just like "Jeopardy," you must form a question. If you are not asking a question, how can you expect an answer? Emails lacking the "?" character are not asking a question, and are moved to the bottom of the queue. Similarly, emails labeled "URGENT" or containing more than three exclamation points are also disregarded. If it wasn't important, why would you bother to ask? (Unless it's Friday afternoon and you're bored.) What is it you were doing? The context of your situation almost always has some effect on what you witnessed. Were you at a computer? Was it turned on? Did you try turning it off and back on again? Was it a "Macintosh" computer? Was it running "Windows?" These answers may hold important clues. What was it the computer did? The actual text on the screen is a lot more valuable than "It didn't work." If there is an error message, it has meaning and will help troubleshoot your problem. If the computer says, "I'm sorry, Dave, I can't do that," well, some problems may be beyond help. What was it you expected the computer to do? If you told it to do something STUPID, and it did something stupid, well, duh. (99% of the time, when the computer does something stupid, it's in retaliation for something you did. Think about that, and review the point above, "What is it you were doing?") What other clues can you supply? For example, "This was the first time I've started this computer" is different from "This application has been running fine for 30 years until I tried running it on WIn10-1903 last night." Or, "I just switched datasets to use the 4Gb of data from the customer." Or "I just changed one little thing." Or "Windows installed updates last night and the screen is all green." What have you tried to resolve this issue? Did you search the error message on the web? Did you look up the problematic line of code in the manuals? The Hacker's Guide? Did you try to reproduce the error? Did you turn off the machine and turn it on again? Did you pack the tables and recreate the indexes? Can you reproduce the error in a few lines of code? Thank you for using ProFox technical support. We appreciate that you have many choices in FoxPro support, and greatly value your loyalty. Please ensure that your tray is stowed, your seat is in its upright position and note that the nearest exit may be behind you. - finis "Boom!" Nice catch, Bill! -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/CACW6n4sfi6C=g_HJGBe62aa=9lqkihbkc1+e_sbzwc-m0fd...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
