Recent content by Toman

At this moment you are perfectly right Mike. I can also see it in the right-hand column. But what I saw today at about 12 a clock is different and you can see it on a screenshot here There is no Microsoft: Visual FoxPro Forum there. This was the reason for my panic behavior. Probably pages...

Hi Has someone noticed, that a reader of Tek-Tips without having our lovely page Microsoft: Visual FoxPro Forum in "My Threadminder" is unable to see it, unless he knows exact location http://www.tek-tips.com/threadminder.cfm?pid=184. In other words: Home > Forums > Programmers > DBMS Packages...

Hi Ali, in similar situations helps me sometimes command element.click() like: oWeb.document.getElementById("loginForm").getElementsByTagName("input")[7].click() where control on a web page must be a type SUBMIT ("input")[7].type="submit" and 7 was an index in one particular case. Even if...

Bart, my code snippet was meant like that * open your page with map IE = CreateObject("InternetExplorer.Application") IE.Navigate ("http://YourGoogleAddress.com") IE.visible = .T. * request for loading page into new explorer window was given here * DISABLE any other possibilities...

What about a BUSY property of Explorer object. Something like: IE = CreateObject("InternetExplorer.Application") IE.Navigate ("http://YourGoogleAddress.com") IE.visible = .T. DO While IE.Busy DOEVENTS ENDDO Bye, Tom

Gentlemen Thank you very much for your valuable information and tips and for giving so much of your time to other people from VFP community. Tom

Mike and Olaf Thanks to your help and inspiration I see now a suitable solution. I'm sending Shift-Ctrl-Alt state as a numeric parameter to form's method MyClick from both MouseDown and KeyPress and I even need not to have temporary storage to these values. So I have only *** in KeyPress method...

What if a client will "click" on a control (with focus) by means of ENTER or SPACE on a keyboard, which is completely legal in Windows. I thought that additional calling MouseDown() from somewhere will fix the problem, but it will not, because no parameters are received by MouseDown procedure...

Ooh shure, DEBUGOUT, this is the right way. And much more better then SCREEN.Print. I need not to send LineFeeds, take care about variable type and output list can be endless and can be copied or saved easily. Thank you Tamar very much. Tom

For debugging I occasionally use commands like _SCREEN.Print(cMyVar + CHR(13)) I think it has some advantages over WAIT WINDOW, MESSAGEBOX. Unpleasant is, that this way I can use only some area of the screen to show results. I have a suspicion, that this part has the same height as the form...

I have found a reason for shuting my VFP down during testing. It has absolutely nothing to do with recommended _screen command. My previous post was written poorly, it was not clear whether I am thanking Mike for knocking down my VFP, or for his tip. Of course I'm thanking him for excellent...

Very interesting thing. It looks like some side effect. _screen.MousePointer = 13 should change mouse pointer if cursor is over a screen, But it works my way. Cursor over a form disappears and comes back after mouse action as I need. Resolving the problem where to return "screen" mouse pointer...

For older VFP version without JUSTPATH lcPath = LEFT(SYS(16),RAT('\',SYS(16))) Tom.

After pressing a key in Textbox or so, mouse pointer disappears and comes back after almost any mouse action. True for Windows and VFP too. Is it possible to simulate this state (mouse pointer disappearing) programmatically? In fact, I can avoid situation when disappearing would be helpful...

Keith, have a look at thread184-1587483 Tom.