A similar problem happens with Visual FoxPro, the bigints fields of
Firebird are translated as character(19)
Why?
No idea, but so it is. The solution is easy, the VAL() function solves the
problem by casting the character(19) field to a numeric field, but at first
it is annoying.
I have to live with that.
Greetings.
Walter.
On Thu, Feb 28, 2013 at 4:41 AM, <bjoern.rei...@fau.de> wrote:
> Hello,
>
> we stepped over a small problem with current odbc driver and MS
> Access:
>
> BIGINT (in our Db primary keys) fields are presented as text 255
> fields in access.
>
> Trying another client via odbc they are presented as flaot fields
> wich seems to be a littel bit better than text 255 but not what I'd
> expect.
>
> Can anybody give me the info where there could be a problem and how
> to get bigint as a number to access via odbc?
>
> There must be a problem in Access as I found people mentioning
> similar problems with MS SQL Server and Access.
>
>
>
>
>
> Björn
>
> --
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> _______________________________________________
> Firebird-odbc-devel mailing list
> Firebird-odbc-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Firebird-odbc-devel mailing list
Firebird-odbc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
