All, I have some vba code that "refreshes" or "updates" the odbc links on some linked oracle tables.
When I moved from office 2003 to office 2007, I starting getting errors when updating from access fields to oracle fields in linked tables.
So I ran an update that reset the connection string.
Orginal Connection String
This connection string produced errors such as "can't update field with a null value". I know the field wasn't null.
Updated Connection String
This new connection string seems to work fine. The update queries work as they did before we upgraded to office 2007.
I got the connection string form the connect field in the MSysObjects table.
What I need to know is ...
1. What are all the possible settings of the odbc connection string?
2. Are any of the settings in the original connection string the cause for why the updates are not working?
David Pimental
(US, Oh)
When I moved from office 2003 to office 2007, I starting getting errors when updating from access fields to oracle fields in linked tables.
So I ran an update that reset the connection string.
Orginal Connection String
Code:
DSN=MYDSN;
UID=user;
PWD=password;
DBQ=MYDBQ;
DBA=W;
APA=T;
EXC=F;
FEN=T;
QTO=T;
FRC=10;
FDL=10;
LOB=T;
RST=T;
BTD=F;
BAM=IfAllSuccessful;
NUM=MS;
DPM=F;
MTS=T;
MDI=F;
CSR=F;
FWC=F;
FBS=64000;
TLO=O;
This connection string produced errors such as "can't update field with a null value". I know the field wasn't null.
Updated Connection String
Code:
DSN=MYDSN;
SERVER=MYSERVER;
DATABASE=;
pwd=password
This new connection string seems to work fine. The update queries work as they did before we upgraded to office 2007.
I got the connection string form the connect field in the MSysObjects table.
What I need to know is ...
1. What are all the possible settings of the odbc connection string?
2. Are any of the settings in the original connection string the cause for why the updates are not working?
David Pimental
(US, Oh)