Switch form from Read Only to Edit 3

[k2a]

Hi to all,
I want to prevent accidental changing data in a form. Command buttons should only allow changing the data on the form.

Just tried to do this by mean of ThisForm.SetAll("Readonly",.F.,"TextBox") and ThisForm.SetAll("Readonly",.T.,"TextBox") but for some reason this does not work.

I would be glad for any assistance.

Regards,
Klaus

 

[Mike Lewis]

One possibility that comes to mind is that your textboxes are subclasses of the native VFP textbox. If that's the case, you need to pass the name of the subclass as the third parameter to SetAll, rather than "Textbox".

Off-hand, I can't think of any other explanation - unless there's something you haven't told us.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips, training, consultancy

 

[DSummZZZ]

Also, that will only apply if the textboxes are located on "Thisform". If the are on a pageframe or some other parent control it won't work.



-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[Olaf Doschke]

Dave, that's not true. Setall works recursing through all layers of a form, also pages of pageframes, containers, inner grid controls, everything.
Also, the third parameter is optional, you can simply say Thisform.SetAll("ReadOnly",.T.)

Bye, Olaf.

 

[k2a]

Hi Mike,
You are right, I used the name from the ParentClass field instead of the subclass. After changing that and then it worked.

Unfortunately, those form was created in earlier days using the form wizard and all textboxes became names like embossedfield, but in the meantime I have my own classes.
Is there a way to change the underlying form’s textbox classes to my classes without redesign the whole form?
What must be done to force the form wizard to use my classes and not the standard classes?

Regards,
Klaus

 

[Dan Freeman]

Is there a way to change the underlying form’s textbox classes to my classes without redesign the whole form?

Your forms are SCX and SCT files, which are just DBF and FPT files in drag. You can USE yourform.scx like any dbf and edit it directly. In this case, find the textbox records and change the CLASS and CLASSLOC fields. Work carefully, and only on backup copies. You can ruin your existing forms.

If it's something you need to do a lot, you can create a builder pretty easily that will do this for you on call. Over the years (decades now), much has been written about writing tools such as builders in VFP. Google can probably find a LOT for you to start with.

What must be done to force the form wizard to use my classes and not the standard classes?

The source code for the wizards ships with VFP so in theory you can make them dance and whistle "Dixie" if that's what you want. BUT... the wizards have never been the best way to work with VFP so your effort would probably be better spent finding other ways to work with the product.

 

[Olaf Doschke]

Dan is right about the wizards. I just want to point out there is the "Field Mapping" tab of the options dialog (Menu:Tools->Options). This is not about the wizards, but about what control you get in a form when using drag&drop from dataenvironment to a form. The wizards use classes you find in Home()+"Wizards", all of that is "open source".

Bye, Olaf.

 

[Mike Lewis]

Is there a way to change the underlying form’s textbox classes to my classes without redesign the whole form?

I use a tool called HackCX, from White Light Computing. As Dan says, you can do the job by hacking the SCX and VCX files yourself, but this tool does it for you in a safe and controlled way. It's not free, but if you do a lot of VFP programming, it will pay for itself many times over. See

http://www.whitelightcomputing.com/prodhackcxpro.htm.

Mike






__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips, training, consultancy

 

[k2a]

Thank you Mike, Dan and Olaf for your great help and very useful advices.
This forum is really amazing and deserves my sponsorship.

Regards
Klaus

 

[k2a]

Thank you Mike, Dan and Olaf for your great help and very useful advices.
This forum is really amazing and deserves my sponsorship.

Regards
Klaus

 

[DSummZZZ]

Dave, that's not true. Setall works recursing through all layers of a form,...

Then I must have been doing something else wrong because it has failed me a few different times.
Oh well. I always get it to work another way.


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[Nifrabar]

In the book 1001 things you always wanted to know about visual foxpro written by Marcia Akins, Andy Kramek and Rick Schummer and publiced in 2000 there is in chapter 12 a (working) tool-example of how to change classes.

Marcia sometimes hangs around here in the forum too; maybe she will give you the code if you don't own the book.

-Bart

 

[TamarGranor]

In addition to the various suggestions provided here for changing control classes, there's also a terrific tool in Thor to do this. It only does one control at a time, but you can do while in the Designer.

Tamar