NTK and The NTK Project
are properties of Jn Dechereux
Home | Documentation | FAQ.

Vanilla 1.1.8 is a product of Lussumo. More Information: Documentation, Community Support.

Welcome Guest!
Want to take part in these discussions? If you have an account, sign in now.
If you don't have an account, apply for one now.
    • CommentTimeSep 14th 2010 edited
    Hi All
    I need a bit of Crystal Reports knowledge(?)
    My (future) new NTK app will need to produce one or two nice printouts.
    Jn tells me Crystal Reports or FastReport is what I need when moving to windows printers and away from PCL5 through an HP on LPT1.
    Jn likes Crystal Reports! I do to, however, it's quite a bit of money! So, I was excited to see a NEW (unwanted) copy of "XI Professional Edition" for sale on UK eBay.

    ...Does anyone know if "XI Professional Edition" will be ok to produce print reports in my multi user db3 app (the seller says HE needs "XI developer", which is why hes selling)
    p.s. I emailed Jn with this question and then remembered I should be using the NTK forum (sorry Jn)
    • CommentTimeSep 14th 2010
    Hi Al,


    The professional Edition is designed for customers or end-users who (eventualy) would like to change or enhance developer reports.

    Actually, you should rather purchase the Crystal XI Developer Edition. This version provides the redistribuable runtime (DLLs kit) needed to be installed on each workstation on which your program is running.

    Hope it helps.

    • CommentTimeSep 21st 2010 edited
    Hi Jn
    I've ended-up buying CR10(developer) (I will be looking for an upgrade to XI ASAP)

    Meanwhile, I thought I'd try a small report using CR10 and then call it up from an NTK app..... (I've some problems please advice...)

    1. Created a report named "REPORT1.RPT" (displays the contents of a small dbf - works fine in CR)
    2. Added a function to a small working NTK app

    a. copied - crpaig32.dll, CRPE32.DLL, ctl3d32.dll & IMPLODE.DLL to the working directory
    b. declaired - PRIVATE cRptName := "REPORT1.RPT"
    c. wrote function -
    FUNCTION SelPrn()
    NTKPRT_CRWRPT( cRptName , "Printing: TEST", 1, 1 )

    My print test app compiles OK however when it runs SelPrn() it crashes and generates
    "Error 525 - This report cannot be printed..." (from RNTKCRYS?)

    I guess theres more to using NTKRPT_CRWRPT() than I've used in my simple test - could you guide me some more?

    • CommentTimeSep 21st 2010 edited
    Hi Al,

    IMO, this is NOT a NTK issue!

    Error 525 =="Unable to load report". Typically, the CR documentation indicates a .dll version conflict.

    However (according to my own experience), you may also encounter this issue when using some UNC path or static path for connecting to db3 databases (i.e. \\myserver\mysharefolder\mytable.dbf or S:\myfolder\mytable.dbf) within a CR report (.RPT) - whilst the network connexion is closed or not existing...

    So, I strongly suggest you to check the following:
    1. For each db3 declared in the .RPT, remove the static part regarding the access path. (i.e. just keep the name+extension of the db3 file).
    2. When invoking NTKRPT_CRWRPT() at runtime, the .RPT file and concerned db3 file(s ) should be located in the same folder. (e.g. the ..\tmp local folder of your app)

    Hope it helps.


    > I've ended-up buying CR10(developer) (I will be looking for an upgrade to XI ASAP)
    Yes, that's a very good idea. CR9 and 10 DOES NOT work correctly with DBF files. XI is far better.
    • CommentTimeSep 21st 2010

    I've got it!!

    I've replaced ntkdic\crpe32.dll (1997 file) with the one which came on the CR10 CD-ROM (2003 file)

    and CR printing is working via my NTK app - great!

    Tomorrow I'm working on CR-Formulas.... whats your tip, should I learn Formula Workshop??

    • CommentTimeSep 25th 2010 edited
    Printing data using Crystal Reports is powerful

    much nicer than what I'm used to...

    @ x,y say "anything"


    I've created several reports called from an NTKdemo app, each which work very well on my machine! The only trouble is......

    Doing the same on my customers PC isn't working!
    Thats simple I thought... move CRPE32.dll along with my demo app and dbf

    but no!!

    Jn has woken me up with the realiaty that I must creat a MSI tool to deploy god knows how many crystal reports dll files on the host systems running any NTKdemo which print using (this very nice) Crystal Report file

    Can anyone give me a clue what to use and how to do this... please???

    thanks (hopefully)
    • CommentTimeSep 25th 2010
    Ok you guys...
    I've a feeling I'm almost their with CR runtime

    found this:

    Who can nip through and suggest the files NTK needs?


    do I have to work it out on my own??

    (...I'd rather be tasting a nice glass of (French) wine)

    • CommentTimeSep 28th 2010 edited
    I've read the manual and I've got Crystal Reports printing from my NTK app on other PC's - great!

    I needed to join SAP Crystal Reports support group as an "end user" (not developer - otherwise you pay!)

    I found and downloaded "cr10_rdc_mm.zip" (I'm using CR10)

    I extracted "CrystakReports10_rdc_ReportEngine.msm"

    I incorporated the comlete MSM bundle straight into a MSI file (using a 30 day free trial copy of "WisePackageStudio", because I couldn't find "freeware" MSI builders which supported MSM??)

    I installed the MSI on other PC's and "hey presto!"

    Database Data, in the form of "very beautiful" reports, are printing directly to the windows printer (or pdf) and, importantly, with no LPT1 or PCL5 in sight! - goodbye clipper hello NTK

    • CommentTimeSep 28th 2010
    Hi Al,

    It's always pleasant to hear such good news.
    Now, you've got your Win32's printing solution working in replacement of your old Dos-Clipper's printout system.
    That's done it! Finally, you can get rid of those old tricks and tips and other workarounds needed to print on usb printers, and all other problems related to the old dos platform!
    I'm very happy for you.
    BTW, thanks for sharing your experience with each of us.