I'm sorry, the attachment doesn't seem to be showing up.
It is a gif animation.
I hope someone can get more inspiration from this than to market this tool.
Its source code has been lost, maybe I'll rewrite it again if I have enough time.
I seem to be late to the party :)
I would like to add that I realized this idea a long time ago.
Simply running some code in the command window of the VFP IDE is a natural way to implement it. But running similar code briefly or frequently is annoying, so I wrote it as a tool, see attached.
You can use Foxhwnd.ocx for this purpose if you stick to the original design. Foxhwnd.ocx can be found in the VFP6 installer, and details of how to use it can be found in the help file.
Hi, KarenLloyd
I discussed your question with a friend (Chinese). He is sure it can be solved in VFP6. However, I don't know how to establish a connection between you and him because the forum doesn't allow to leave an e-mail address. Do you have a good suggestion?
Simply put, you can use MemberData for this purpose.
For example, you have two attributes: test and testdesc. then, you can write the following script through MemberData Editor:
If Aselobj(LoSelobj) = 0
Aselobj(LoSelobj, 1)
Endif
If LoSelobj[1].Test = 1
LoSelobj[1].Test = 2...
Public oform1
oform1=Newobject("form1")
If Vartype(oForm1) = "O"
oform1.Show
EndIf
Return
*
Define Class form1 As Form
DoCreate = .T.
Caption = "Form1"
lload = .F.
Name = "Form1"
Add Object command1 As myCommand With ;
Top = 24, ;
Left = 12, ...
What I've described is not outdated and simply requires the DynamicCurrentControl property to be used again.
It's something like this:
With Grid
With .Column1
.DynamicCurrentControl = "iif(Recno() = 1, "myImage", "myCombo")"
EndWith
EndWith
An example of this technique...
You want each current control in a separate column to use its own data source if I understand you correctly.
There are usually two ways to accomplish this:
1 Use the dynamic properties of Column;
2 Using the control's BackStyle_Access method.
I usually use the second method because it's easier...
Chriss,
Whether you define the SelectCMD property or add any code to BeforeCursorFill/BeforeCursorRefresh, it is normal just in the normal case.
But once CursorRefresh is executed in a VFP transaction, everything becomes unbelievable and the correct result is not obtained.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.