Recent content by phirst

  1. P

    Crystal Reports

    Hi Sandra, Try this: DEFINE VARIABLE hCRParams AS COM-HANDLE NO-UNDO. DEFINE VARIABLE hCRParFld AS COM-HANDLE NO-UNDO. DEFINE VARIABLE iCRCnt AS INTEGER NO-UNDO. ... /* don't prompt user for parameters */ hCRRpt:EnableParameterPrompting = FALSE. /* parameters */...
  2. P

    odbc & char-fields

    Hi, If you are using v9 there is a new field "SQL-WIDTH" which defines the size of the field in SQL-92, it is usually defined twice as big as the normal format. If not, you will have to increase the FORMAT, this does not change the CRC of the table, so you will not have to recompile, though it...
  3. P

    Regular App need to change

    Hi Octavio, I have had some major schema changes to handle with in the past. I had all the programs under UNIX and I used a 'sed' script to change the table and field names. This worked fine for 95% of the programs. The other 5% took a few days to sort out, the compilation showing us the...
  4. P

    Progress v9 & Crystal Reports RDC

    Hi all, I am using Progress v9.1a and Crystal Reports 8 RDC. I have one problem to which I just CANNOT find the solution, and I have checked out all the forums and sites I know. I connect to CR8: DEF VAR chSCR AS COM-HANDLE NO-UNDO. CREATE "CrystalRuntime.Application" chSCR...
  5. P

    Storing archives in a Progress database

    Hello again, I forgot to say that the RAW data-type is limited to 32K, so, above this size you will have to cut the file up. This is trick shown in the KB entry (progresstalk reply). Cheers, phirst.
  6. P

    Storing archives in a Progress database

    Hi Ted, You would be better off using a RAW field to store your zipped file. A character field is not designed to stock binary data, this is why the nulls are converted to spaces. Bye, phirst.
  7. P

    Migration 8.2b to 9.1b

    I have tried both methods for converting V8 db's to v9. The conversion tool (proutil -C conv89) seems to me the best approach. It's certainly a lot quicker and surer. Convert the v8 db into a simple multi-volume (1 data and 1 bi extent) and trunc that bi before hand. As for multi-volume...
Top