FiveTech Software tech support forums

... but somewhat less than you in that I use xDATAFILE via class properties rather than direct inheritance. 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 ...

Doug, >>> I take your point about "scatter / gather" but please note that scatter/gather could be implemented in my architecture (not subclassing xDATAFILE class but merely pointing to it) equally as in your architecture. >> I'm ...

Hi James >> I take your point about "scatter / gather" but please note that scatter/gather could be implemented in my architecture (not subclassing xDATAFILE class but merely pointing to it) equally as in your architecture. > I'm sure ...

... advantages of OOP is using inheritance to make things simpler, and I think that you are not fully understanding it. >I take your point about "scatter / gather" but please note that scatter/gather could be implemented in my architecture (not subclassing xDATAFILE class but merely pointing to ...

... in the belief that if we both explain our ideas both of us and potentially others listening in will be the wiser for it. I take your point about "scatter / gather" but please note that scatter/gather could be implemented in my architecture (not subclassing xDATAFILE class but merely pointing to ...

... are tremendous. >I did deviate a little from your methodology in that I have a DATAFILE_Class but that doesn't do automated "gather and scatter" - I think that's what you called it? It does however control the allocation of keys and the standard fields included in all my tables which ...

... and fun once I got started. I did deviate a little from your methodology in that I have a DATAFILE_Class but that doesn't do automated "gather and scatter" - I think thats what you called it? It does however control the allocation of keys and the standard fields included in all my tables which ...

... to use them as you will save hundreds, maybe thousands, of lines of code in your applications. With a database object you don't have to use any scatter/gather functions and there is no dealing with aliases. There are lots of other good reasons to use objects too. Below is the code without a ...

... DbGotop() IF !lMode bBlock := {|val,elem| Fieldput(elem,f_isOEM(@val,elem))} ENDIF DO WHILE !Eof() oMeter:Set(nActual+1) SysRefresh() aData := Scatter() Aeval(aData ,bBlock) dbSkip() ENDDO DbUnlock() oMeter:End() oGaugeDlg:End() sysrefresh() RETURN NIL FUNCTION scatter(nInicial,nFinal) local ...