Originally posted by: SystemAdmin

Hi, everyone,

I m solving an optimization model using ILOG and the results are designed to be written back to a MS ACCESS database using DBUpdate function.

I have ran the same problem using the same database on two computers with the following configuration,

Configuration A: 32 bit ILOG CPLEX & MS ACCESS 2007

Configuration B: 64 bit ILOG CPLEX & MS ACCESS 2007

On computer A, everything runs through. Whereas on computer B, the model did solve the problem, but 2 of the 7 output tables cannot be written back to the MS ACCESS database, error message shown as follow,

"Database error(state = 22001 code = 31):[Microsoft][ODBC Microsoft Access Driver] String data, right truncated, near setOutCost".

Does anyone has the same issue? Any thought?

Any help is appreciated.

Thanks,
#CPLEXOptimizers
#DecisionOptimization

Originally posted by: AgustinPecorari

Hi,

I'm having the same problem, no matter which database (Access, SQL Server). I'm using 64 bit ILOG CPLEX.

I'm reading from database without problems. Even the oil example doesn't work properly.

Did you solve the problem?

Thanks,

 

Agustin.

#CPLEXOptimizers
#DecisionOptimization

This could be unrelated, but it reminded me that running 32-bit and 64-bit versions of Office on the same computer is not supported.  Do you happen to have a 32-bit version of Office installed (or the 32-bit version of the ACE Drivers)?  If so, you might try uninstalling the 32-bit version of Office and re-installing the 64-bit version.

 

Also, if you're using OPL, you might have better luck getting an answer on the OPL using CPLEX Optimizer forum.

 

#CPLEXOptimizers
#DecisionOptimization

Originally posted by: AgustinPecorari

I'm using 64 bit Office. 

On the same machine I've created solutions using CPLEX  through Concert and VisualStudio. They work properly writing on the same Access database.

The problem is only with OPL. I'll try on the OPL forum.

Thanks.

#CPLEXOptimizers
#DecisionOptimization

Originally posted by: VincentBeraudier

can you try by putting the dbUpdateBatchSize setting to a low value such as 1 for example?

It may solve the problem and show the DB driver has a bug

#CPLEXOptimizers
#DecisionOptimization

Originally posted by: AgustinPecorari

I tried  dbUpdateBatchSize = 1, but I still get the same error.

Just for information. This command works fine:

t_SalFue to DBUpdate(db, "INSERT INTO tbl_SalFue(nodo) VALUES('Test_txt')");

But this one doesn't:

t_SalFue to DBUpdate(db,"INSERT INTO tbl_SalFue(nodo) VALUES(?)");

I'm working on a fresh installation of windows 7, 64 bits, CPLEX Studio 12.5 64 bits, Office 64, SQL Server 2012 (Spanish).

I tried different drivers.

#CPLEXOptimizers
#DecisionOptimization

Originally posted by: AgustinPecorari

Hi,

Did anyone find an answer to this problem?

Thanks,

 

Agustín.

#CPLEXOptimizers
#DecisionOptimization

Originally posted by: PhilippThurnher

Hi,

is there an answer to this problem? The Oil-Example does not run on ILOG CPLEX 64 bit, no matter what Office Installation (32 or 64 bit). Please help me!

Thanks,

Philipp

#CPLEXOptimizers
#DecisionOptimization

Originally posted by: PhilippThurnher

#CPLEXOptimizers
#DecisionOptimization