Search results for query: *

How about you, Chris? Any idea?

Everything's just fine except for step 4 of your instructions, Mike. From the FAQ: You can modify the toolbar by choosing 'View / Toolbars...' from the menu. Now you can select the toolbar, and with the customize button you can modify it. Yep, I want to modify it alright. However, I cannot...

Well, okay, I'm stupid. But I can't figure out any way to remove the printer icon from the print preview toolbar. I read the FAQ and the FoxPro help topic. I followed the instructions, dragging the printer icon off. All that did was create a new toolbar. Had another programmer give it a go...

Bravo! Got to ponder the problems this might introduce for the users, but it sounds promising. I'll give it a run tomorrow and let you know what I decide. Of course I'd prefer being able to either directly alter(correctly) the Data memo or call a FoxPro function(wish-list item). Again, thanks...

Guess this is a 'wish-list' thing for me then. Thanks again, Mike.

Thanks, Mike, but I was looking for a way to conditionally remove that icon during runtime. It would be a boon to my life if I could do that.

You can remove the print icon from the print preview toolbar window? How?

If I understand what you're asking, you want to know if there is something environmental that you can detect from within your application when a user clicks the printer icon in the print preview toolbar window. Not that I could ever find. The solution I came to was to detect a mouse click in...

Just so you'll know for future reference, VAL() is working correctly(as designed). If the leftmost characters of the string are numeric the function returns the value of that portion of the string.

Or just COMP Myfile at the command line would be easier than shutting down and restarting Fox.

Thanks for the post, StuckWith26(like that's a bad thing). Your solution seems completely illogical, just as mine does. I guess I should have done a smoke-and-mirrors act when I 'fixed' it the first time, and become a local god. Zog is so smart! Yeah, right. We did another release a few days...

So I've given up on the idea of eliminating the problem menu bars from the menu pad popups and will control the user's preferences to get most of what I want. Too bad I can't find a way to give them the Show Grid and Show Position, but that's in the View pad, which is a definite no-no for me...

Yes, it is, Harry. You might also want to read the RELEASE PAD, DEFINE PAD and DEFINE BAR topics. Sorry, I'm at home now, and most of my FP is at the office, but here's a bit of old code to get you going. It won't do anything spectacular since you don't have the full code, but give it a run...

You'll want to look into SET SYSMENU TO, Harry. Check out SYS(2013) for a list of the system menu names.

SET STATUS BAR OFF should do the trick.

The application I am working on exposes the Report Designer to the user to allow modification of the report. The problem is that the system menu contains items in the View popup that we want the user to have and items that we cannot allow the user to have. For instance, we want the user have the...

I used to get power failure header damage on a regular basis, and wrote my own recovery routines, using low level file commands. It's been a while, so I'm not prepared to write the step-by-step for you, but it can be done. My method was a bit different than trying to correct the file length...

If your initial state is SET EXCLUSIVE OFF when you open the table, issuing SET EXCLUSIVE ON does not give you exclusive use of the file, which is required for the PACK command. After issuing the SET EXCLUSIVE OFF you could SELECT the target table, issue a USE DBF() EXCLUSIVE command and then...

You left the 'NOCONSOLE' arguement out of your SELECT, Lyn. Can't help you with the Excel problem. Good luck! --Zog

Thanks, Mallee, but that's a no-go. What you're describing smells of a cache issue to me. The behavior I have is definitely not data related. I'm beginning to think it's maybe demons. My logic insists it has to be introduced quietly in the compile process. CSteenbe's post seems to be the very...