Re: Acc20: Write-conflict on records in newly created Oracle-Tables

Martin Schroeder wrote:
>
> In <4v13ru$5h1_at_izb.izb.de> snie_at_izb.de (Stefan Niemeyer) writes:
> >ms_at_dream.hb.north.de (Martin Schroeder) wrote:
 

> >>...
> >>We create a new table like another, add the keys, copy the data from the
> >>source table -- and when I then attach this table with MS-Access, I get
> >>a write-conflict-warning from MS-Access on _some_ records in the table
> >>(but not all!). :-(
 <snip>
> >NUMBER(10,3). I'm not sure if the ODBC driver 1.11.002 still have this<snip>
>
> Absolutely strange -- but this might be the cause.
>
> The new driver will arrive next week anyway...
>

I would guess this is the problem. We have the same bug with ODBC to our Teradata DB. I checked the ODBCAPI Log and it looks to me that Access converts something like NUMBER(10,3) to a float! Microsoft tells me there is no problem with Access, it must be AT&T and AT&T says it must be Access. But because this happens in Oracle and others I would guess MS should look into it.

But, let me know if the new Oracle drivers fix this, because then I lose my argument that MS needs to release a fix.

We use a lot of $ amounts defined as DECIMAL(8,2) and a lot of them can not be updated with Access as attached tables.

Steven

-- 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Steven Drinovsky                      sdrinovsky_at_wic.tdh.state.tx.us +
+ Texas Department of Health,                      home (512) 453-2317 +
+ WIC Automation                              work (512) 458-7111x3476 +
+ My opinions are my own and by no means represent the state of Texas. +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I think so, Brain, but if we didn't have ears, we'd look like weasels.
	-Pinky, from Pinky and the Brain, Battle for the Planet