FiveTech Software tech support forums

Silvio: Without being rude, I use both of them and I only see advantages in the 2nd one (unless you clarify the point): 1st method: (at least 5 lines)  LOCAL oDlgP, oProg1   DEFINE DIALOG oDlgP FROM 1, 1 TO 5, 44 ;       TITLE "Initial configuration" @ 1, 2 PROGRESS oProg1 SIZE 135, 12   A...

Ahhhhaaaaaaaa! I answer myself: :mrgreen:   FUNCTION ReportToExcel(oBrwI, aData)        MsgMeter( { | oMeter, oText, oDlg, lEnd | ;                  ToExcel ( oMeter, oText, oDlg, @lEnd, oBrwI, aData) },;                  "Sending data to Excel", "Please stand by..." )     RETURN...

Thanks for your kind responses. Sorry, but I meant without using a dialog, only the advantages of MsgMeter (if there is a simple way). There is also a oText and oDlg object there, so maybe... You cannot beat one line of code with at least 20 lines of creating and administrating yourself a dialog :( ...

To everyone: I want to know if there is a simple way to change the message in a MsgMeter like in the following code: FUNCTION ReportToExcel(oBrwI, aData)    MsgMeter( { | oMeter, oText, oDlg, lEnd | ;              ToExcel ( oMeter, oText, oDlg, @lEnd, oBrwI, aData) },;              "Sending dat...

I have the following problem when using CreateIndex to create temporary indexes: //1st function        USE Clients Alias clients SHARED NEW        DATABASE oDbfC        //temporary index CreateIndex( [cFile], cTag, cKey, [lUnique], [lDescend], [lMemory] )                oDbfC:CreateIndex( nil, "...

After reading carefully your answer, I try something similar to pointers in C which worked perfectly: // Problem solved here using AADD to fill arrays #include "fivewin.ch" STATIC oDlg     FUNCTION Main()        LOCAL aData[3][3], ; //MUST be the same dimensions as the final array         ...

OK. Understood. New array=will not update (strange that will show the old one). Mr. Otto, of course I only skip 1 and -1, as I explain, this is only a test program, Nothing to do with a real case. Just done to illustrate AADD vs array assignation and how they show (or not) in a Dialog. And no, delet...

Here is a mini working example: To notice before you answer: 1. I do not use browse in this example, but my tabbed dialogs are full of them as well as lists, images, comboboxes, date fields, buttons, slide-shows, reports, Excel conversion, SQL queries, and everything else that works correctly 2. I c...

I'm not saying that it does not works. IT works to show the dialog the 1st time, but as the user skips from register to register the dialog does not update, it keeps the old values.

Doing it assigning values to a predefined array, on the other hand, works perfectly showing the values every time.

After noticing that a tabbed dialog only updated partially, I finally realize (5 hours later) that if I fill-up the culprit array using: aCalif:={} ... AADD(aCalif,{chCta, Others[INT(chCta+.5)+1] ,thCta, Others[int(thCta+.5)+1], ;                    (chCta+thCta)/2, Others[int((chCta+thCta)/2+.5)+1]...

Thanks, so I abandon the other structure until a further version? :D Something (imaginary) like nIDGet:= 64 nID    := 108 FOR nIDVar := 23 TO 30     REDEFINE GET oGet GetSUBSCRIPT nIDGet VAR aPedg VarSUBSCRIPT nIDVar,2 MEMO ID IDSubstript nId OF oFld:aDialogs[4] UPDATE READONLY FONT oFuente[2]     n...

Thank you for your advice. We have now two cases: * This one works: nID:=116 FOR nIDGet := 47 TO 62     REDEFINE GET aPedg SUBSCRIPT nIDGet,2 ID nID OF oFld:aDialogs[4] UPDATE READONLY FONT oFuente[2]     nID++ NEXT * This one, a little more complex, has an error E0030 on GET nIDGet:=  64 nID   := 1...

Thanks. That make it work, but then the whole structure is useless since it attach all the GET array to one ID.

At least it narrows the error down to the IDSUBSCRIPT part that seems to be giving the problem (and error)

Emiliano Llano Díaz

Mr. Navarro: Thanks for your concern. Maybe in that one, but in the other one? (gives same cryptic error): .\prg\register.PRG(783) Error E0030 Syntax error "syntax error at 'GET'" * Original code * REDEFINE GET aPedg[47,2] ID 116 OF oFld:aDialogs[4] UPDATE READONLY FONT oFuente[2] nIDGet:=...

Mr. Rao: Thanks for your answer. I did try that combination (among another dozen ones that, of course, I do not remember) in despair but I got this enigmatic error: .\prg\register.PRG(777) Error E0030 Syntax error "syntax error at 'GET'" Same for this code: * original: *REDEFINE GET oGet[6...