FiveTech Software tech support forums

... client runs a high volume shipping service and they do not like any additional clicks. If there is a way to be able to save this report as a pdf (naming it, and deciding where it lands on the drive) would greatly help. I have been using CDO, and PDF995 and this has not worked well. I have already ...

Maurizio,

Do they use some special naming or there are no rules at all in their names ?

... in unix systems to allow their own * i18n to be enabled. So, this variable should be found in an average * unix enviroment, and it will have the naming scheme that we have * proposed above. TODO: remove the '@' lang extension, like * it_IT@euro * * If you don't have access to the LANG variable, ...

... := GRAPH_TYPE_XY_AQ To something like this: oChart:nType := GRAPH_TYPE_XY //AQ I am assuming AQ are your initials? The above change just keeps the naming consistent with the existing ones. If you care to share this modified class with everyone, then I would also first make sure you have the latest ...

... := GRAPH_TYPE_XY_AQ To something like this: oChart:nType := GRAPH_TYPE_XY //AQ I am assuming AQ are your initials? The above change just keeps the naming consistent with the existing ones. If you care to share this modified class with everyone, then I would also first make sure you have the latest ...

... the object starts working on a different DBF. We resolved this issue by changing ( ::nArea )-> with ( ::cAlias )-> and managing the alias naming system to avoid any possible repetitions. We also noticed another issue with METHOD Use(). Multiple calls to Use() when the object is already ...

... get access to all the data and methods of the object. Encapsulation is one of the doctrines of OOP. Another doctrine of OOP is polymorphism (same naming). So it would be better to name the method "Print" and use the same name for other classes too. This way you can pass any object to ...

... statement after specifying all settings. Thanks. Obviously, I didn't know that. It is now in my notes. This is one reason that polymorphism (like naming) is important and useful in OOP. If the syntax for the browse was: DEFINE XBROWSE oBrw...ACTIVATE BROWSE oBrw Then there would be less chance ...

... project and add all my .prg back in and much to my surprise I had a file named Rview .prg ( notice the extra spaces ). After correcting my DOS naming error .. I was able to re-create my xMate project list and was able to get a successful run-time break with the error.log and dialog. For whatever ...

... removing itself from its parent oTree DATA aItems. Now it is ok. * New: function SetCurDir( cDirName ) --> lSuccess, to match GetCurDir() naming. * Fixes: Method ToExcel() of XBrowse and Report are not working propery in case of some Excel international installtions. Fixed * Fix: Class ...

... But the database class already does this in it's Close method so you can just do this: oDBF:close() Actually, to be consistent with standard naming (polymorphism) it technically should be: oDBF:end() But our TDatabase class doesn't have an End() method so we have to use the Close() method. ...

... up to 8 char .. Try this and see what happens .. Copy *.rc MyForms.rc .. then compile the monolithic MyForms.rc and see if you get an error or naming conflict ?? I have found some strange problems like you are describing show up especially if you have a lot of forms. Rick Lipkin

... , russian and all invoices and packing-slips in english also . So the cyrillics it's needfull for me . With lithuanian I can write , as we are naming "tongue-tieded" ... :) , without nat.chars "ąčęėįšųūž" . At first I saw problem with cyrrilics notes ... Any ideas ? With ...

... Yes, your bStrData definition is correct. You must also tell TXBrowse that you are using a database object: oBrw:SetoDBF( oArqEmp ) May I suggest naming your database object after the realworld object, for example "oEmployees." This makes the code easier to read and understand, especially ...

Maybe it's a matter of naming. One doesn't expect that a method called SetBrush() creates a brush but merely assigns an existing one. So, why does it have to increase the brush counter as if it's creating one?

EMG