FiveTech Software tech support forums

... dFecha TEMP->(__dbZap()) TEMP->(dbAppend()) oDlgAlb:Update() oBrw:Refresh() Return nil la función Inicampo, es similar al Gatter/Scatter de clipper, o a las funciones Load/Save de Database, simplemente inicializa una matriz con el tipo y longitud de campos de la tabla que se la ...

... to index files to locate a element without scanning a array (i suppose , i am not a specialist) Also the syntach is much easier. In clipper i scatter the elements with LOCAL h[FCOUNT()] , i := 1 AEVAL(h,{||h[i]:=FIELDGET(i++)}) RETURN h To use i have to replace fieldnames with fieldnumbers ...

With xHarbour you cann use HASH aDati := TAssociativeArray() aDati:c1 := "WWWW" aDati:c2 := "eeeeee" You cann simulate Scatter and gather of the record //------------------------------------------------------------------------- FUNCtion Scatter() Local aVars := {=>} LOcal nField ...

... overcome these issues. >> As Otto showed, it does not. >What Otto showed is how you program around the issue - that is you automatically scatter/gather what you can and manually do the rest. It splits the code for a data object into multiple places which I don't really like. But that ...

... programs and printers work). > As Otto showed, it does not. What Otto showed is how you program around the issue - that is you automatically scatter/gather what you can and manually do the rest. It splits the code for a data object into multiple places which I don't really like. I am not ...

... to either their data structure or your application. >It makes sense to add your own data types (stored as text) but that pretty much blows scatter/gather out of the water. As Otto showed, it does not. James

... thought to be yes / no ends up with a third possibility. It makes sense to add your own data types (stored as text) but that pretty much blows scatter/gather out of the water. But if there is an existing data object that returns data as xml then its easy to use your existing UI and BL layers ...

Doug, >>Why? I take the opposite position. If they are aware of the fields, then there is MUCH less coding required-in fact for the gather/scatter there is no coding required. Even if you don't wish to use this feature, why would it be a negative? >Because when you want your software ...

... very useful >Why? I take the opposite position. If they are aware of the fields, then there is MUCH less coding required-in fact for the gather/scatter there is no coding required. Even if you don't wish to use this feature, why would it be a negative? Because when you want your software to ...

Doug, >>> My only point would be that automatic scatter gather means that the UI layer has to be aware of the fieldnames used by the data layer. >> They are. >But it would be preferable if they didn't need to be. Why? I take the opposite ...

Hi James >> My only point would be that automatic scatter gather means that the UI layer has to be aware of the fieldnames used by the data layer. > They are. But it would be preferable if they didn't need to be. > I suggest thinking about ...

Doug, >My only point would be that automatic scatter gather means that the UI layer has to be aware of the fieldnames used by the data layer. They are. >Clearly the Read(), Write() and Blank() methods of my classes can be automatically generated ...

Hi James I am 100% with you on that. My only point would be that automatic scatter gather means that the UI layer has to be aware of the fieldnames used by the data layer. Clearly the Read(), Write() and Blank() methods of my classes can be automatically generated ...

... called. (Data was passed as xml.) Whilst my code isn't exactlly three tier, it does pretty much conform to the general idea. If you use automated scatter/gather as I understand its current form, then your UI layer has to be aware of the field names that data is stored under. That becomes a problem ...

... date() ::lastTime:= time() return super():save() >I don't currently use any form of generic scatter / gather but I do buffer all data and updates are only written after the user confirms that they want to update / write. (Actually I mostly ...