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 Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

first, next prev, last, "wizbtns.vcx"

Status
Not open for further replies.

kaelong

Programmer
Jan 8, 2008
12
US
OK This is my first time utilizing the MENU automation. (*.mpr) I'm sure this is a simple thing, I just simply don't know what it is. I've never utilize it before, so before .MPR I could place PUBLIC variable in the "MAIN.PRG" that would carry throughout the program that I needed, for one. Second, I'm finding using a MENU.MPR it's is not the same. I've had to adjust already, which is fine, but for my form for "Customers" the WIZARD - first, previous, next, last etc. buttons it does not recognize my reference to where the bmp's for the button's are. It reports back as an error of sorts. Where as before there was no problem, in the version before the MPR. What an I missing? The error say something like, "operand missing".
 
Kaelong,

What exactly is your problem? You mentioned MPRs, public variables, bitmaps and a "missing operand" message. But it's not at all clear what you need to know.

If you are getting an error message, I suggest you post the code that is causing the message, along with the exact wording of the message. If you don't know which code is causing it, use the Suspend button (in the error messagebox), and then open the Trace window in the debugger. This will point to the code causing th error.

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

My Visual FoxPro site: www.ml-consult.co.uk
 
Like Mike, I'm not sure exactly what your problem is, but I do know that if you're using public variables, you should rethink the logic that requires them. Public variables are far more trouble than they're worth.

Tamar
 
Thanks guys, I will have a chance to look at it more in depth in a day or so. I will see if I can't pin point the code with the error on the buttons. I think I have solved the issue with the PUBLIC Variable, as Tamar said, by rethinking that logic.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top