FiveTech Software tech support forums

... "oDBF." But you can have something like oCustomer and oInvoice open in the same routine since there is no name conflict. Using these conventions makes your code very easy to read and understand, even years after you wrote it. James, I have 57 fields I not know wich field the function ...

... "oDBF." But you can have something like oCustomer and oInvoice open in the same routine since there is no name conflict. Using these conventions makes your code very easy to read and understand, even years after you wrote it.

... dedication! 15. It's way cooler than reading! 16. Its a creative outlet! 17. It's something to do when you're bored! 18. You get to go to away to conventions and meet other people who share your interest! 19. It's a way to make money to afford all the new toys, books, and other neat stuff! 20. ...

... The calling convention to use for the DLL function can optionally be specified. Constants are available for this parameter. Calling conventions Constant Value Description DC_CALL_CDECL 0x0010 C calling convention (__cdecl) DC_CALL_STD *) 0x0020 Standard convention for WinAPI (__stdcall) ...

... This function loads a file containing a table and stores it in * an xharbour array. If a filename is given, that won't follow the * i18n() opening conventions: you will have to use a full valid * relative or absolute filename to open the file. * * On success, the returned array has two elements. ...

... as "Extended Literal Strings". Syntax: ------- E"..." The literal string may contain Escape Codes following the C language conventions, like: \n -> New Line character. \t -> Tab character. \r -> CR character. \" -> literal <"> character. \' -> ...

James, from the MSDN, GetWindowRect() function: In conformance with conventions for the RECT structure, the bottom-right coordinates of the returned rectangle are exclusive. In other words, the pixel at (right, bottom) lies immediately outside the rectangle. ...

... The Class Ribbon was end ? and the other option and features of this class where are ? As you are very new to the forum you can't know the conventions. But you have no right to get an answer in this forum. All the people here help for free. I think you can get paid support from Fivetech. ...

... substituded by a array from 4 elements : { cHeading , nWidth , cFooting , Field number/name or CodeBlock } 4) 2) and 3) may be mixed. Using these conventions , we can always ( array from dbf) : 1) oCombox := Txcombox():new( , Arrfield , ….) First parameter NIL !!!!! 2) Change column properties ...

... FiveWin classes. I rather gather that we can use namespaces to overcome this but I was thinking that it might be good to sort out some naming conventions before we get too far. Regards Doug

... 99.51 and fwh 2006 using xharbour 99.71 and fwh 7.09, gpf occurs with getproc32() and I never get to the calldll32. If I use the "old" calldll conventions, most calls work in 99.71 but not all - this was not a problem with 99.51. If I use the calldll32 conventions, I get gpf on getproc32() ...

... itself. I think that any such system would, for many of its features at least, be highly dependant upon the programmer's programming styles and conventions and rely upon them being applied fairly consistently. Any such system is likely to work much more effectively with code that was written ...

... and S_VOTERS etc. After I dropped the "S_" in the resource names, the problem disappeared. Perhaps there was some conflict with Win API naming conventions. So beware of naming resources with an underscore in this way, especially "S_". -------------------------------- - Roger Roger Unfortunately ...

... and S_VOTERS etc. After I dropped the "S_" in the resource names, the problem disappeared. Perhaps there was some conflict with Win API naming conventions. So beware of naming resources with an underscore in this way, especially "S_". -------------------------------- - Roger