Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Messagebox() with 4096/8192 vs Form's AlwaysOnTop

Status
Not open for further replies.

torturedmind

Programmer
Jan 31, 2002
1,052
PH
Dear All,

I encountered this just now. Here's the scenario. I have two forms - one being the parent which fills the entire screen and where the encoding takes place, and the other, a smaller one, where a grid resides to show the user some reference data. I set the smaller form's AlwaysOnTop property to .T. so the user can switch back and forth the two forms without closing the reference data form (smaller one). The problem is that, any MESSAGEBOXes are not shown if the smaller form is active or shown even if I add the parameter 4096 or 8192. I know the messagebox is active somewhere (probably behind all forms) as both forms loses focus and I cannot exit the app thru normal means. Any idea on how to go around this predicament?

TIA

kilroy [knight]
philippines

"Once a king, always a king. But being a knight is more than enough."
 
I forgot to mention, my dev PC is Win 10 Pro with VFP9 SP2, if that matters.


kilroy [knight]
philippines

"Once a king, always a king. But being a knight is more than enough."
 
Please disregard this query. It turned out the newer compiled app is stored somewhere and am still using the older version. Sorry for causing some commotion. I think I need to call it a day. [banghead]

kilroy [knight]
philippines

"Once a king, always a king. But being a knight is more than enough."
 
No need to apologise, Kilroy. These things happen to us all. But thanks for letting us know that you solved it.

We haven't seen you around here for a while. I hope you are sill enjoying your VFP work.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads
 
I tracked down a similar problem of code changes not applying even with a collegue developer looking over my shoulder and we even took a few days before realizing compilation should help. In my case the code was not an EXE but an APP, which was used in the nature of a library, ie NEWOBJECT("class","some.vcx","some.app") was used, but that's buried in some init routine. So it really happend and much worse than in your case even with four eyes looking at it.

Bye, Olaf.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top