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

Wzbtns

Status
Not open for further replies.

quakeunity77

IS-IT--Management
Jun 3, 2010
36
US
I keep on getting the error message memo file wzbtns.vct is missing or invalid. I tried copying the file from another computer and substituting the new file with no luck.
Any suggestions?
 
Try this:

1. Make sure both wzbtns.vcx and wzbtns.vct are in the same directory.

2. Add wzbtns.vcx to your project, then do a Build. Tick "Rebuild project" and "Compile all files".

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro tips, advice, training, consultancy
Custom software for your business
 
I have both the wzbtns.vcx and .vct in the same directory. I did "Rebuild project" and "Compile all files".

I tried that several times with no success.
 
Hi,

Wzbtns.vcx and Wzbtns.vct come with the original installation disk. If everything fails, just update (reinstall) VFP and your wzbtns class will be replaced with a working one.

Jockey2
 
The files were not set to read only on attributes but I noticed that the permissions did not inlcude "write" so I change them to "write". That did not help. I have the same problem
 
I have tried to recompile the class but I still get the error message. I have copied the files from the the original installation disk but I still get the error.
 
You've been referring to these files as wzbtns. I thought I'd try to open wzbtns.vcx myself to see if I got the same error. But the file is not present in my VFP install directory. I do have wizbtns.

Is it possible that the file you are using is not the one that comes with VFP (it would normally be installed in the Wizards directory)?

Either way, there's obviously some confusion about the filenames.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro tips, advice, training, consultancy
Custom software for your business
 
I am sorry if I misspelled the title on the original post. I meant to say wizbtns.vct from the start and that is the name of the file. I wish that I could change the title on the post.
 
I had same problem few time. Just VFP reported that mentioned class isn't presented and offer button Locate. In most cases with this move I solved problem but I don't understand why this problem appeared today and yesterday all was fine? Maybe problem with hardware, e.g. hard disk: simply in some moment VFP loosed a detail about vcx in project...?

There is no good nor evil, just decisions and consequences.
 
Is there a bug in VFP 9? I get the wizbtns.vct missing error often and then it disappears!!
 
As far as I see it's up to contents and liability of project where problematic form belongs. probably in some moment VFP didn't push right info at right place and ... voila. In some future moment VFP then fix it by itself like reindex fix sometime table. I guess not sure at all.

There is no good nor evil, just decisions and consequences.
 
One of my solutions is to save project under different name and sometime in different folder; then I change name of former folder and issue recompile whole project. Don't know why VFP occasionally make such things.

There is no good nor evil, just decisions and consequences.
 
I now have the problem when I am building a new form with the form wizard. It will stop at the end and state that wizbtns.vct is missing or invalid. I build the form by hand with no problem and include the wizbtns class and I can compile the project.
 
I am experiencing a similar issue right now. My work around is to run VFP as an administrator (right mouse on the desktop icon and choose "run as an administrator". Until I figure out why I need to do this.

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.
ReFox XI (www.mcrgsoftware.com)
 
If UAC is on and you sometimes start VFP as admin and sometimes not OR if you are running VFP with different users. Compiling a project the classlib files within ffc get virtualized, if you're not admin and the files get not virtualized, if you are. And as this always is a set of two files needing to match in case only one of them is virtualised the next time you start VFP in another mode or another user you will have a mismatch and thus the error.

Either always start VFP as the same normal user or always as admin via the run as admin context menu item.

Have a look at C:\Users\...yourwindowsaccountnamehere...\AppData\Local\VirtualStore\Program Files\Microsoft Visual FoxPro 9\Ffc

and you may find the witns.vcx/vct. Delte them there, the original files should be in the Program Files, they are protected against overwriting, as long as you don't run as admin.

Solutions:
1. Don't install VFP into Program Files
2. Give yourself write permission into the VFP Program directory and subdirectories, so files are not stored into the VirtualStore directory.

Either way now you've got compromised ffc files, rather reinstall.

Bye, Olaf.
 
Olaf said:
Solutions:
1. Don't install VFP into Program Files
2. Give yourself write permission into the VFP Program directory and subdirectories, so files are not stored into the VirtualStore directory.

Or .....
3. Copy all source files to a location not controlled by UAC, which is the best solution for "working" files anyway

;-)
 
Hi Dan,

Yes, that's pretty sure the best solution for all self made foxpro sources anyway. But if using FFC and the wizards the ffc code is rather convoluted with indriect references of other classes via the HOME() function and thus copying part of the FFC classes somewhere else is not always a working solution.

That's another reason to stay away from wizards and all the other ffc stuff and go with any decent vfp aplication framework instead or roll your own.

But if you go with what comes with VFP, installing VFP in a free directory or adding write permissions to the default installation directory are working solutions to get rid of the VirtualStore problem. It double bytes VFP users, as many
things foxpro are in a bunch of two or three files.

Bye, Olaf.
 
bites of course. It bites VFP users double in comparison of other applications or programming languages, for which the VirtualStore method is rather transparent but still has the issue of a per user VirtualStore.

In my oppinion everything in Program Files is for all users and thus should be put in a VirtualStore directory of the ALLUsers or Public User.

Bye, Olaf.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top