Re: NewEra3.1 Connection to AccessDB

I never tried this on an Access DB but maybe it helps. autocommit with no lock ?? In windows start event : CALL ixSQLconnect::getImplicitconnection().setconnectoption( ixSQLConnect::SQL_Autocommit, NEW ixInteger( 1 ) ) # SQL_Autocommit 1 = On (default)0 = Off ixInteger FUNCTION setConnectOption( option SMALLINT, param ixValue) RETURNING VOID This function sets options that affect a specific behavior for the referenced connection. For CCL/ODBC, the option argument must be one of the eight options that the first column of the following table shows. For CCL/Informix, the only valid value for the option argument is SQL_Autocommit. The param argument is an ixValue object that contains the desired value (either an integer or a string) for the specified option. The third column of the table shows the appropriate ixValue types (ixInteger or ixString) for the option values. Option Option Value ixValue Type SQL_Access_Mode SQL_Mode_Read_Write (default) SQL_Mode_Read_Only ixInteger SQL_Autocommit 1 = On (default)Enables manual-commit mode0 = Off Enables auto-commit mode ixInteger Regards Marco Rene van Luijt wrote: > We started working with Informix NewEra only a few weeks ago, trying to > get a connection to a Microsoft Access database via ODBC. > > At the moment we are able to connect to the database and READ the > records (which we inserted through MS Access directly). If we try to > insert new records via our NewEra application these records can only be > applied and retrieved temporarily. If we quit and restart the > application the records are no longer there (they are not written to the > database, as we can see if we inspect our tables using MS Access). > > We would like to know if anybody has already experienced the same > behaviour and could give us some advice. > > Rene van Luijt > University of Koblenz > docu@uni-koblenz.de