Description

This example demonstrates how to integrate GAMS into a Microsoft Office Access
2010 application. Both the GAMS model and input data is in Access. When the
model is solved a temporary file ".gms" is created, which may be convenient
to edit during GAMS model development. The GAMS execution process can be
viewed, interrupted and stopped from Access. The model data is transferred
to GAMS using the GAMS GDX VBA API to create a GAMS Data Exchange (GDX) file.
After GAMS has solved the model the result is transferred into Access via a
comma-separated values (CSV) file.

Developed with Visual Basic for Applications 7.0.1628, 10/31/2013.

Contributor: Toni Lastusilta

Category : GAMS Data Utilities library

Main file : SpawnGAMSAccess.gms   includes :  SpawnGAMSAccess.gms  SpawnGAMS.accdb

$title  SpawnGAMS: Spawn GAMS from Access
$onText

This example demonstrates how to integrate GAMS into a Microsoft Office Access
2010 application. Both the GAMS model and input data is in Access. When the
model is solved a temporary file ".gms" is created, which may be convenient
to edit during GAMS model development. The GAMS execution process can be
viewed, interrupted and stopped from Access. The model data is transferred
to GAMS using the GAMS GDX VBA API to create a GAMS Data Exchange (GDX) file.
After GAMS has solved the model the result is transferred into Access via a
comma-separated values (CSV) file.

Developed with Visual Basic for Applications 7.0.1628, 10/31/2013.

Contributor: Toni Lastusilta
$offText

$callTool win32.msappavail Access
$if errorlevel 1 $abort.noError "No Access available"

$call "start SpawnGAMS.accdb"