Comments on: Report Writer for 7.1 http://clarionsharp.com/blog/2009/08/report-writer-for-71/ Simply the fastest tool available for creating custom database applications! Fri, 20 Jan 2012 19:27:17 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Robert http://clarionsharp.com/blog/2009/08/report-writer-for-71/comment-page-1/#comment-43 Robert Wed, 19 Aug 2009 18:12:52 +0000 http://clarionsharp.com/blog/?p=162#comment-43 Hello, We never send out our dictionary ... it is proprietary. Currently, using Clarion 6 Report Writer, they connect directly to the TPS or SQL files. If the TPS layouts change (ie: we add a new field), the current RW stops the user and tells them they can't run the report without opening up the TXR, and doing FILE / IMPORT / TPS FILE / etc. 1. Is there a way for this to be made automatic. It would be a HUGE benefit 2. When working with an SQL database like Sybase SQL Anywhere, is it possible for you to read the COLUMN DESCRIPTION from the database when displaying the fields to pick from in the new report writer. This would make it so the user did not even need a dictionary because the column description is actually embedded in the SQL database. If you need an example of what we do, I can provide it. Hello,

We never send out our dictionary … it is proprietary. Currently, using Clarion 6 Report Writer, they connect directly to the TPS or SQL files.

If the TPS layouts change (ie: we add a new field), the current RW stops the user and tells them they can’t run the report without opening up the TXR, and doing FILE / IMPORT / TPS FILE / etc.

1. Is there a way for this to be made automatic. It would be a HUGE benefit

2. When working with an SQL database like Sybase SQL Anywhere, is it possible for you to read the COLUMN DESCRIPTION from the database when displaying the fields to pick from in the new report writer. This would make it so the user did not even need a dictionary because the column description is actually embedded in the SQL database. If you need an example of what we do, I can provide it.

]]> By: rzaunere http://clarionsharp.com/blog/2009/08/report-writer-for-71/comment-page-1/#comment-41 rzaunere Wed, 19 Aug 2009 16:08:40 +0000 http://clarionsharp.com/blog/?p=162#comment-41 The "library" (.repxl) is a simple XML file, but the reports (.repx) have a lot of changes and additional data in them to support Clarion functions, Clarion# code, data dictionaries, drivers, etc. so I don't think it will be possible to open them using Devexpress libraries. Likely we'll change the reports extensions to avoid confusion. The “library” (.repxl) is a simple XML file, but the reports (.repx) have a lot of changes and additional data in them to support Clarion functions, Clarion# code,
data dictionaries, drivers, etc. so I don’t think it will be possible to open them using Devexpress libraries. Likely we’ll change the reports extensions to avoid confusion.

]]> By: Graham Dawson http://clarionsharp.com/blog/2009/08/report-writer-for-71/comment-page-1/#comment-39 Graham Dawson Wed, 19 Aug 2009 12:45:39 +0000 http://clarionsharp.com/blog/?p=162#comment-39 Hopefully the next Webinar won't be plagued by the same 'gremlins' :) Will the new RW Library file (.REPL ?) be a readable unencrypted TPS superfile ? ie will we be able to access the individual .REPX report files etc This would open up ReportWriter to individual and 3rd party developers who wish to produce their own front ends etc using Clarion.NET and DevExpress components. Hopefully the next Webinar won’t be plagued by the same ‘gremlins’ :)

Will the new RW Library file (.REPL ?) be a readable unencrypted TPS superfile ?
ie will we be able to access the individual .REPX report files etc

This would open up ReportWriter to individual and 3rd party developers who wish to produce their own front ends etc using Clarion.NET and DevExpress components.

]]> By: rzaunere http://clarionsharp.com/blog/2009/08/report-writer-for-71/comment-page-1/#comment-37 rzaunere Wed, 19 Aug 2009 12:03:47 +0000 http://clarionsharp.com/blog/?p=162#comment-37 Yes, we understand that and we'll have a separate DLL for accessing the new reports, and we'll ship both DLLs so users can work with either format. Yes, we understand that and we’ll have a separate DLL for accessing the new reports, and we’ll ship both DLLs so users can work with either format.

]]> By: Robert http://clarionsharp.com/blog/2009/08/report-writer-for-71/comment-page-1/#comment-30 Robert Tue, 18 Aug 2009 23:00:04 +0000 http://clarionsharp.com/blog/?p=162#comment-30 Thank you. This sounds good. Will the C70PRLBX.DLL be smart enough to run both TXR and REP's so we can maintain old legacy reports, or will you have two different DLL's? Please don't add a new parameter to the existing call, otherwise, it would break compatibility or at least default it to legacy. Make sense? Thank you. This sounds good.

Will the C70PRLBX.DLL be smart enough to run both TXR and REP’s so we can maintain old legacy reports, or will you have two different DLL’s? Please don’t add a new parameter to the existing call, otherwise, it would break compatibility or at least default it to legacy.

Make sense?

]]>