Does other Office for Mac applications encounter the same issue? Only Microsoft Word. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.
Threats include any threat of suicide, violence, or harm to another. Any content of an adult theme or inappropriate to a community web site. Any image, link, or discussion of nudity. Any behavior that is insulting, rude, vulgar, desecrating, or showing disrespect.
Any behavior that appears to violate End user license agreements, including providing product keys or links to pirated software. I have monitored taskman in the past and while the working set value does rise via pop3 login it appears to drop off and remain steady until the next login.
The Timers that Martin mentioned are in another sub project which isn't used for the testing of the attached project in this thread. Please see my comments above.
I appreciate the DoEvents details. Here's my modification. This piece of info might or might not have a direct relevance to your current case, given here just for your longshot reference. Action1 Action It took me a long time to discover that, but once discovered, a solution was easy. This phenomenon didn't always appear; I now can't recall whether it was depending on how quick the user's mouse action or how long the Action2 took.
Remarks: The specific reason for adding a DoEvents was to enable user to drag to scroll picDisp in the viewport on a non-active child form immediately on its becoming active, e. Without the said DoEvents, the user would have to click to set focus to that form first, then mouse down to scroll picDisp. Last edited by petersen; Aug 8th, at AM. Attached Files Form1.
I think whether it helps or creates conflicts may depend on what code it's preceded or appended too. Techsent Attached Files Form1. The way your code is now your obr9f, a, i, j, and k variables will never contain anything because you fill hhh and then immediately set it to vbNullString.
If you don't set it to vbNullString the variables willl all contain the same value. The following is some code that shows both cases. Paste it into a new project and try it. VB will create the file if it's not already there even though you specified Append. The hhh variable will not be empty once the keyword is processed from the pop3 email.
The code spins through all the emails in the inbox. Once it finds the keyword, the hhh will then contain the keyword. If you run the whole project, it will give a demo.
I've changed up the code to use append only. Techsent Yes, it will, because you set it to vbNullString immediately after it is filled. And even if that is not the case, all the obr9 variables that I mentioned will have the same thing in them. Is that what you want? I could have used 1 variable and passed it to main timer44, timer Strictly speaking, in the DataArrival event you should not assume you have a complete response from the server when you issue the GetData.
You are employing buffering on the RETR but not on any other response. The responses from POP3 are quite short so it's unlikely that they will split into two or more parts, however it is possible which could lead you to report errors when there weren't any, or the application exploding when you try to unblock the count of messages into AmtMessages.
I have, in the past, experienced a 10 byte message being split into two 'parts' by the underlying protocols. It's only at that point you know for sure you have a complete response from the server. If you do that you have to clear strData1 after processing the contents. Perhaps things to put on your "To Do" list after the current problems are resolved. I'm still worried about the number of Timers and the fact that you have more than one running at the same time.
This next part may be 'off the wall' but I'm still thinking about whether it's possible or not so don't take it too seriously In the extreme, if, say, Timer3 is always triggering 'early' then I estimate that after 6 days it would be nearly 4 minutes out - I can't see if and where you stop Timer3. After 6 days the Timer3 code proper has executed about times - interesting that it's not too far away from , I wonder if there's a 4K limit to something in VB If the other timer is running 'late', one may catch the other up As I said, 'off the wall', could be absolute nonsense, but I'm still trying to get my head round it.
Is there any reason why you can't just start a timer, when 2 minutes, or whatever, have elapsed, stop the timer, execute the 'business' code, re-start the timer and go round the loop? That way any inaccuracy of the timer doesn't matter since there's only ever a maximum of 1 timed asynchronous event. You will also process the complete message queue in one hit. At the moment you have a maximum of 2 minutes to process the queue then you close the socket whether you've finished or not Another 'off the wall' thought, if there's some sort of 'issue' with Winsock getting its buffers in a twist, I wonder whether using a dynamic Winsock instance and Unloading it when you've closed it which should destroy it completely, freeing up internal buffers etc , then Loading a new instance before configuring it for connection, would eliminate any problems.
You'd be starting with 'a clean sheet' wrt Winsock every time you connected to the server. Amongst other things, that SP fixed a few Winsock issues including leaking memory. The problem with this problem is that you will never know if it's fixed and if it is, how you did it!!!
I had to add the DoEvents because the email flagged for deletion wasn't getting deleted after logging out and back in. Good point on the DataArrival event. I discovered that before using the msgbox command. It would hit many times in one session. I'll check into it. I've been trying to implement your technique Load Winsock1 1 , Unload Winsock1 1 but need some guidance.
I have set the index properties of winsock1 to 0. Added Index As Integer to all winsock code headings. Next, I configed this. Close Winsock1 intwinsck. Hardly definitive evidence of an ongoing bug.
Originally Posted by OnErrorGoto0. That was a trial version of Excel It may be an issue with the OS, or a hardware conflict. I note the coincidence of one user in that thread mentioning the error occurring after his screensaver kicked in for instance. You've shown a few people experiencing an intermittent issue, but you yourself have it working in Excel on a different machine, which would imply to me that if there is a bug, it is not necessarily in If it's not related to OS or hardware, why does it work on one of your machines?
The only other thing I can suggest that you might try is not using the default instancing of the forms - declare a variable and use that, then destroy the variable when done. It's more likely to be a bug in the Forms Library FM Originally Posted by Riggers. If a hardware conflict or an OS issue is causing Excel to do this which I personally think is unlikely.
The word 'unlikely' is the key Any testing I've done on various potential solutions has always involved closing and reopening Excel.
I don't have teh code available to me now as I'm at work but I displayed a new instance of the form something like this:. How did you load the original form? Removing the forms completely is the only way I've found of solving this.
Add "facebookForm" I'm guessing so will post the actual code later tonight and hopefully a simple version if I can recreate it. If you forgot your password, you can reset your password. JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding. You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser. Joined Jun 26, Messages Hi all, This is blowing my mind! I have the following piece of code which I have been testing:- Code:. Excel Facts. Easy bullets in Excel. Click here to reveal answer.
Joined Aug 20, Messages 3, If you click Help from the error message you get this text This error has the following causes and solutions: The file specification isn't correctly formatted.
0コメント