Than you very much for the answer...

But only one question because I don't understand...

My problem isn't at the code(VB) level (perhaps it is a consequence!) but on odbc/table level..

With your explanation I think the problems occur, as you said, in odbc level.. In fact already when I attempt to open linked tables in access I find this problem in few records (a lot of others, instead, are correct).. Only for open a table, without query or vb code, but only with doble click..

You suggest also to cast data... So I ask you: how I can cast data if I can't work on casting? In fact the schema of a linked table in access can't be changed; ad so for firebird tables because the firebird db is of a third part comapany.. For the data is the same thing: neither I' can't intercept exception nor i can't cast decimals that raise error.. In fact I can't interfer between firebird and access when table are linked and opened.. It is an autoamtic operation of access through odbc driver..


My last hope is firebird-odbc-support.. I'll try to ask them if there is a solution... Do you have an email address or a link to a forum or support area to go and speak to?

Thanks...

--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@...> wrote:
>
> At 09:14 PM 12/10/2009, you wrote:
> >Hi to All,
> >
> >I'm a programmer
> >
> >I'm using an Access 2000 database with Access 2003. I linked some Firebird tables via ODBC. Most tables work just fine, but there's some that give me the error "The decimal field's precision is too small to accept the numeric you attempted to add."
> >
> >This error occurs on just a few records. I'm able to open the table and see my data except for those few records, they show as "#Error"
> >
> >I need these tables to be linked and can't change their design as they are used be another application wich can't be updated...
> >
> >Any ideas ?
>
> Look at the definitions (data type and precision) of the corresponding columns on each side and figure out what the mismatch is. You might be able to approximate a match by casting one or the other as a varchar. On the other hand, maybe you have a genuine overflow situation that *should* throw an exception that your application will need to handle.
>
> I'd recommend taking your question to firebird-odbc-devel as there might well be some magic checkbox that will deal with the problem in the interface layer. We don't do driver stuff on this list.
>
> ^ heLen ^
>