DataFlex Reports: Difference between revisions

From DataFlex Wiki
Jump to navigationJump to search
m (moved Visual Report Writer to DataFlex Reports: Visual Report Writer was renamed to DataFlex Reports during product rebranding exercise)
m (Changed Visual Report Writer to DataFlex Reports)
Line 1: Line 1:
Visual Report Writer is a software tool for delivering timely, well organized reports and information to the people that need it.  
DataFlex Reports (originally called Visual Report Writer) is a software tool for delivering timely, well organized reports and information to the people that need it.  


Designed to be used by end-users, power-users and professional software developers alike, Visual Report Writer works with a wide variety of data sources including Microsoft SQL Server, IBM DB2, Oracle, MySQL, Pervasive SQL, PostgreSQL, Microsoft Access, the DataFlex embedded database and more.
Designed to be used by end-users, power-users and professional software developers alike, DataFlex Reports works with a wide variety of data sources including Microsoft SQL Server, IBM DB2, Oracle, MySQL, Pervasive SQL, PostgreSQL, Microsoft Access, the DataFlex embedded database and more.
''Quote from [http://www.visualreportwriter.com/ www.visualreportwriter.com/]''
''Quote from [https://www.dataaccess.eu/products/dataflex-reports-245]''


=Some tips and tricks=
=Some tips and tricks=

Revision as of 14:58, 27 November 2017

DataFlex Reports (originally called Visual Report Writer) is a software tool for delivering timely, well organized reports and information to the people that need it.

Designed to be used by end-users, power-users and professional software developers alike, DataFlex Reports works with a wide variety of data sources including Microsoft SQL Server, IBM DB2, Oracle, MySQL, Pervasive SQL, PostgreSQL, Microsoft Access, the DataFlex embedded database and more. Quote from [1]

Some tips and tricks

Data

  • Works very nice with record oriented DataFlex Embedded database
  • Works great with ODBC Set oriented databases
  • Works ok with INT mechanism where the set oriented database is accessed on record by record basis (Use only for convenience on small datasets)