Miscellaneous Group

All content on the site should (must?) belong to a group. This group is the catch-all for content that doesn't fit anywhere else.


org.eclipse.emf.ecore.sdo.edit_2.1.0.

Code Share


Org.eclipse.emf.commonj.sdo_2.1.0.

Code Share


License

Eclipse Public License - Version 1_0


EMFT-JET-SDK-0.7.0

Code Share


Plug-in: org.eclipse.jet_0.7.0.v200606260942

Code Share


Plug-in: org.eclipse.jet.ui_0.7.0.v200606260942

Code Share


Plug-in: Org.eclipse.draw2d_3.2.0.v20060626

Code Share


Plug-in: Org.eclipse.gef_3.2.0.v20060626

Code Share


Groovy is so darn cool

I'm using the syntax tree from Proparse+ProRefactor, and the Groovy language, to generate XML data about procedures in an application. I want to generate XML with entries that look like this:

<tableref table='customer' create='true' write='true' delete='true' />

prosql

Often I have needed to integrate Progress Databases with other applications. These applications have a horrible time talking to Progress. Yes, I know, “But, but, but there is the ODBC and JDBC connections!”
Well, that is nice if you are on Windows. I am on UNIX or some non-Progress supported operating system or using some form of middle-ware (read that as PHP, Perl, etc.) to make the integration with. Sometimes it has ODBC, sometimes it doesn't.
Sometimes it is a device that needs to interact with Progress DBs and the infrastructure just is not there.


pro2myv2 amduus edition

Use of CLI tools for exporting of Progress schema and data to MySQL with Amduus modifications to Mark Newnham's Pro2myv2 Open Source tool.

The open source tool pro2myv2 has been modified by Amduus to be more UNIX oriented. (It originally was GUI oriented and can still be used in a GUI environment.) This way it can be used from a non-GUI environment and from cron for automatic data exporting and loading from Progress to MySQL.

Attn: This tool requires a developers or query license for the version of Progress it is being used on.


pro2my or pro2myv2

Pro2My is a simple group of PROGRESS source code routines that can be run against any PROGRESS database greater than version 6 to produce a series of files containing MySQL format SQL statements. These files can be used to produce a MySQL database that is a mirror of the PROGRESS database. The routines provide a method of:

  • Extracting the data schema from the PROGRESS database
  • Checking and converting PROGRESS data to prevent MySQL database load errors.
  • Extracting the data from the PROGRESS database.

pro2mysql

Interface for Progress 4GL to query mysql databases.
Functions work like they do in php.

code: browse the code in the Subversion repository http://www.oehive.org/amduus/pro2mysql/

contributed by Matthew Lang


pro2jdbc

pro2jdbc - Progress to JDBC interface

pro2jdbc.p usage:

  1. Run pro2jdbc.p as persistent procedure then open server connection usging jdbcOpenConnection() (that two steps might be done at the beginning of your application).
  2. Run several selects using jdbcExecuteQuery(), retrieve records using jdbcGetRecord().
  3. Finally close connection using jdbcCloseConnection() and remove persistent procedure (that two steps might be done at the end of your application).

http://www.oehive.org/amduus/pro2jdbc/


Session Variable Manager

The variable manager is a super procedure which can replace the functionality usually provided by SHARED and GLOBAL-SHARED variables, as well as adding functionality such as access permissions.

See "SessionVariableManager" in Amduus code repository: http://www.oehive.org/amduus/

by Tim Keuhn


#
Syndicate content