Home   |   MAV Direct ODBC   |   MAV direct ODBC Template version

MAV direct ODBC Template version

It is a full clone of the standard templates (with some extra) for easy work with the library. This is just a template, library is not included.

For the moment available templates:

BrowseBox - clone of the BrowseBox with the extended additional possibilities like:

1. Sorting of any column in BrowseBox by pressing header and Indication of sorting in the column header:

2. Entry / incremental locator with the possibility of filtering of records in the BrowseBox in two modes - usage of additional filters + Locator filter, or only Locator:

3. Data Update Button. BrowseBox is not sensitive to lose / gain window focus, Refresh may take place only obviously having specified it.

Type N and OK becomes red (to be Refreshed)

Press red OK

4. Popup menu constructor for Locator field as well as for Browse List:

5. Visual Where statement constructor in the template:

6. Different type of the BrowseBox Filters: Check Filter, List Filter, Entry Filter, Lookup Filter and Arbitrary Filter.

7. DropLists.

BrowseButton - BrowseBox depended button, you can set some conditions also.

BrowseSelectButton - extended analogue of the standard SelectButton.

BrowseUpdateButtons - extended analogue of the standard UpdateButtons.

Extended build in SQL auto number mechanism. Used FileUserOption in the Dictionary and special table for store number.

LookupButton - extended analogue of the standard LookupButton.

SaveButton - Write record to a Data file. 3 modes of editing:

Table - analogue of the standard mode

View - editing of several records from SQL View (in BrowseBox)

Queue - buffered child records, will be saved in the Parent transaction (for example, Invoice header and Detail records).

Other powerful template coming soon!!  

Try the  DEMO application for Template version !

In this DEMO there is a new more flexible setting for server's connection and creating a test tables used.

For this used:

1. INI file (located in the same directory) with the section for each server:

[oracle]

[mssql]

[mysql]

[sybase]

for "unknown" to us server section has a name  [ODBC Driver]

For example:

[MSSQL]

ConnectString=SERVER=[SERVER]; DATABASE=[DATABASE]; UID=[USER]; PWD=[PWD]

Script=mssql.sql

[MYSQL]

ConnectString=SERVER=[SERVER];DATABASE=[DATABASE] ;UID=[USER];PWD=[PWD];OPTION=3

Script=mysql.sql

[ORACLE]

ConnectString=DBQ=[SERVER]; UID=[USER]; PWD=[PWD]

Script=oracle.sql

where:

ConnectString - how the connection string should be formed rule, text in the [] will be replaced with the

LogIn parameters (Logon window)

[SERVER]   - Server

[DATABASE] - Database, if necessary

[USER]     - User name

[PWD]      - Password

Script - sql script file for the tables creation, there are oracle, mssql, mysql, sybase server scripts in this DEMO.

If you have selected server different from these you will be prompted File name for the script.

Script file - just a normal sql script with the [] fields - this is a Table name used in the DEMO program.

The sign of the End is sql commant - blank line.

Take a look at DEMO script for more info.

If you have unknown for us SQL server and created Connection string and SQL scripts please send us this info info@ingasoftplus.com

We will include your server in a future demo version.